| From: | Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Order of update |
| Date: | 2025-04-21 17:58:56 |
| Message-ID: | bbcfa678-f88a-44f0-91aa-9491262a482e@gelassene-pferde.biz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks for the pointer. I feel my doubts reflected. For such reasons, I prefer the UUID as surrogate key. No point in trying to establish an order or even id arithmetics.
21.04.2025 18:44:27 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:
> On 4/21/25 09:12, Thiemo Kellner wrote:
>> I wonder if that is a corner case. Updating a unique key sounds to me like a design flaw in the first place.
>>
>
> Check out this the thread below for discussion on that topic:
>
> https://www.postgresql.org/message-id/dkbnfi$7g5$1@sea.gmane.org
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marcelo Fernandes | 2025-04-22 01:22:50 | pg_get_serial_sequence not working for manually set seq |
| Previous Message | Adrian Klaver | 2025-04-21 16:52:34 | Re: Cannot turn track_counts on |