| From: | Ivan Voras <ivoras(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Making a unique constraint deferrable? |
| Date: | 2017-02-28 17:05:13 |
| Message-ID: | CAF-QHFWx21fp0zAp_8Evt3NGXOt0304QvKbwJn_exvs0C-zY2A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 28 February 2017 at 18:03, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Tue, Feb 28, 2017 at 9:50 AM, Ivan Voras <ivoras(at)gmail(dot)com> wrote:
>
>>
>> ivoras=# alter table foo alter constraint "foo_a_b_key" deferrable;
>> ERROR: constraint "foo_a_b_key" of relation "foo" is not a foreign key
>> constraint
>>
>>
> A more clear error message would be:
>
> EROR: cannot alter non-foreign key constraint "foo_a_b_key" of relation
> "foo"
>
> Though I'm not sure how that meshes with the error message style guides...
>
Any idea what underlying technical reason prohibits marking non-fk
constraints as deferrable?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-02-28 17:10:43 | Re: Making a unique constraint deferrable? |
| Previous Message | David G. Johnston | 2017-02-28 17:03:13 | Re: Making a unique constraint deferrable? |