From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Jeroen Ruigrok/asmodai" <asmodai(at)wxs(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: constraint modification on todo list |
Date: | 2003-09-08 20:41:42 |
Message-ID: | 200309082041.h88KfgP27748@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Jeroen Ruigrok/asmodai <asmodai(at)wxs(dot)nl> writes:
> > can someone add:
> > Add an ALTER TABLE MODIFY CONSTRAINT
> > item to the todo list?
>
> Why? For a constraint, it's not obvious what this would do for you that
> dropping and re-adding the constraint wouldn't do. In the places where
> we support CREATE OR REPLACE, it's because it's important to maintain
> continuity of the object's identity, but I don't see any need for that
> with respect to check constraints.
I assume MODIFY would allow you to alter the constraint without
re-checking all the rows, as would be required by DROP/ADD. However, if
you are modifying the constraint, wouldn't we have to recheck all the
rows anyway. Of course, one idea would be to allow MODIFY to make
changes that _don't_ require rechecking, but I have no idea what such
changes would be.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Mayer | 2003-09-08 20:42:11 | Re: ISO 8601 "Time Intervals" of the "format with time-unit deignators" |
Previous Message | Doug McNaught | 2003-09-08 20:41:18 | Re: pgsql in shared lib |