Re: WIP: System Versioned Temporal Table - Mailing list pgsql-hackers

From Surafel Temesgen
Subject Re: WIP: System Versioned Temporal Table
Date
Msg-id CALAY4q8ETRoFLBR8qz1P=SNskBBW5z-Kr90t_XGrm9mc9zCEbQ@mail.gmail.com
Whole thread Raw
In response to Re: WIP: System Versioned Temporal Table  (Vik Fearing <vik.fearing@2ndquadrant.com>)
Responses Re: WIP: System Versioned Temporal Table  (Vik Fearing <vik.fearing@2ndquadrant.com>)
List pgsql-hackers


On Fri, Oct 25, 2019 at 10:45 PM Vik Fearing <vik.fearing@2ndquadrant.com> wrote:
>
>     I don't understand what you mean by this.
>
>
>
> The primary purpose of adding row end time to primary key is to allow
> duplicate value to be inserted into a table with keeping constraint in
> current data but it can be duplicated in history data. Adding row
> start time column to primary key will eliminate this uniqueness for
> current data which is not correct  


How?  The primary/unique keys must always be unique at every point in time.

From user prospect it is acceptable to delete and reinsert a record with the same key value multiple time which means there will be multiple record with the same key value in a history data but there is only one values in current data as a table without system versioning do .I add row end time column to primary key to allow user supplied primary key values to be duplicated in history data which is acceptable 

regards
Surafel

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: alternative to PG_CATCH
Next
From: Pavel Stehule
Date:
Subject: Re: Proposition to use '==' as synonym for 'IS NOT DISTINCT FROM'