From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | Rod Taylor <pg(at)rbt(dot)ca>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE modifications |
Date: | 2003-11-14 13:59:05 |
Message-ID: | 1068818345.1620.143.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Rod,
I tried the current patch on a RC2 release, and I noticed one
undesirable side affect.
Modifying a column moves it to the end. In high availability situations
this would not be desirable, I would imagine it would break lots of
code.
Dave
On Thu, 2003-11-13 at 11:35, Hannu Krosing wrote:
> Rod Taylor kirjutas N, 13.11.2003 kell 16:59:
>
> >
> > Can you please suggest a better term to use in place of TRANSFORM?
> > Perhaps UPDATE WITH?
>
> or perhaps USING, based loosely on our use of USING in CREATE INDEX ?
>
> ----------
> Hannu
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2003-11-14 14:13:48 | Re: Help with count(*) |
Previous Message | Andrew Dunstan | 2003-11-14 13:08:40 | Re: heads up -- subtle change of behavior of new initdb |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2003-11-14 14:17:32 | Re: ALTER TABLE modifications |
Previous Message | Andrew Dunstan | 2003-11-14 13:08:40 | Re: heads up -- subtle change of behavior of new initdb |