Re: [GENERAL] spi/timetravel: unique constraint violation on UPDATE - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] spi/timetravel: unique constraint violation on UPDATE
Date
Msg-id 30827.1500156193@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] spi/timetravel: unique constraint violation on UPDATE  (postgresql@get-experience.com)
List pgsql-general
postgresql@get-experience.com writes:
> Den 15. juli 2017 23:15, skrev Tom Lane:
>> Perhaps you could make your PK be on (id, valid_from, valid_to).

> Doesn't really work because valid_to would change on UPDATE. I'd need to
> update foreign relations with another trigger which would be very ugly.

Um ... wouldn't ON UPDATE CASCADE help?

            regards, tom lane


pgsql-general by date:

Previous
From: postgresql@get-experience.com
Date:
Subject: Re: [GENERAL] spi/timetravel: unique constraint violation on UPDATE
Next
From: Karsten Hilbert
Date:
Subject: Re: [GENERAL] How to drop column from interrelated views