On Tue, Jan 26, 2021 at 12:51 PM Vik Fearing <v...@postgresfriends.org> wrote: > > On 1/26/21 1:16 PM, Simon Riggs wrote: > > On Tue, Jan 26, 2021 at 11:33 AM Vik Fearing <v...@postgresfriends.org> > > wrote: > >> > >> On 1/11/21 3:02 PM, Simon Riggs wrote: > >>> * UPDATE foo SET start_timestamp = DEFAULT should fail but currently > >>> doesn't > >> > >> I'm still in the weeds of reviewing this patch, but why should this > >> fail? It should not fail. > > > > It should not be possible for the user to change the start or end > > timestamp of a system_time time range, by definition. > > Correct, but setting it to DEFAULT is not changing it. > > See also SQL:2016 11.5 <default clause> General Rule 3.a.
Thanks for pointing this out. Identity columns don't currently work that way. -- Simon Riggs http://www.EnterpriseDB.com/
