| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
| Cc: | Ryan Lambert <ryan(at)rustprooflabs(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Surafel Temesgen <surafel3000(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Rémi Lapeyre <remi(dot)lapeyre(at)lenstra(dot)fr>, Eli Marmor <eli(at)netmask(dot)it>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Georgios <gkokolatos(at)protonmail(dot)com> |
| Subject: | Re: WIP: System Versioned Temporal Table |
| Date: | 2021-01-26 12:51:13 |
| Message-ID: | 3a53c363-3e3f-813f-ad2f-c2f25ba8f006@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/26/21 1:16 PM, Simon Riggs wrote:
> On Tue, Jan 26, 2021 at 11:33 AM Vik Fearing <vik(at)postgresfriends(dot)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.
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2021-01-26 13:26:06 | Re: WIP: System Versioned Temporal Table |
| Previous Message | Daniel Gustafsson | 2021-01-26 12:49:32 | Re: Allow matching whole DN from a client certificate |