From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Amul Sul <sulamul(at)gmail(dot)com> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Joel Jacobson <joel(at)compiler(dot)org> |
Subject: | Re: NOT ENFORCED constraint feature |
Date: | 2025-01-28 16:17:07 |
Message-ID: | 08667caa-c6d1-4693-a194-6474e1420db6@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28.01.25 11:58, Amul Sul wrote:
>> This behavior is not correct:
>>
>> +-- Changing it back to ENFORCED will leave the constraint in the NOT
>> VALID state
>> +ALTER TABLE FKTABLE ALTER CONSTRAINT fktable_ftest1_fkey ENFORCED;
>> +-- Which needs to be explicitly validated.
>> +ALTER TABLE FKTABLE VALIDATE CONSTRAINT fktable_ftest1_fkey;
>>
>> Setting the constraint to enforced should enforce it immediately. This
>> SQL statement is covered by the SQL standard. Also, I think it's a
>> better user experience if you don't require two steps.
>>
> Let me clarify: the constraint will be enforced for new inserts and
> updates, but it won't be validated against existing data, so those
> will remain marked as invalid.
Yes, I understand, but that is the not the correct behavior of this
command per SQL standard.
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2025-01-28 16:24:59 | Re: Extended Statistics set/restore/clear functions. |
Previous Message | Chapman Flack | 2025-01-28 14:54:51 | Re: XMLDocument (SQL/XML X030) |