From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT |
Date: | 2018-03-07 18:19:18 |
Message-ID: | CAJghg4KqiOZHG4TOxTHOhNOhyJ_NXPgHrG1eD1ySQLAvon8LFw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg배트맨 토토SQL |
Em 3 de mar de 2018 19:32, "Peter Eisentraut" <
peter(dot)eisentraut(at)2ndquadrant(dot)com> escreveu:
On 2/20/18 10:10, Matheus de Oliveira wrote:
> Besides that, there is a another change in this patch on current ALTER
> CONSTRAINT about deferrability options. Previously, if the user did
> ALTER CONSTRAINT without specifying an option on deferrable or
> initdeferred, it was implied the default options, so this:
>
> ALTER TABLE tbl
> ALTER CONSTRAINT con_name;
>
> Was equivalent to:
>
> ALTER TABLE tbl
> ALTER CONSTRAINT con_name NOT DEFERRABLE INITIALLY IMMEDIATE;
Oh, that seems wrong. Probably, it shouldn't even accept that syntax
with an empty options list, let alone reset options that are not
mentioned.
Yeah, it felt really weird when I noticed it. And I just noticed while
reading the source.
Can
you prepare a separate patch for this issue?
I can do that, no problem. It'll take awhile though, I'm on a trip and will
be home around March 20th.
You think this should be applied to all versions that support ALTER
CONSTRAINT, right?
Thanks.
Best regards,
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2018-03-07 18:40:49 | Re: csv format for psql |
Previous Message | Matheus de Oliveira | 2018-03-07 18:10:43 | Re: [PATCH] Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT |