From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: add column .. default |
Date: | 2003-06-19 14:29:36 |
Message-ID: | 1056032975.39060.12.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2003-06-19 at 10:05, Alvaro Herrera wrote:
> On Thu, Jun 19, 2003 at 09:52:14AM -0400, Rod Taylor wrote:
> > On Thu, 2003-06-19 at 09:40, Tom Lane wrote:
>
> > Do we want them to? If we don't mind them being executed, it is far
> > easier to:
> >
> > - alter table structure
> > - Add all new constraints (without confirming their correctness at that
> > time)
> > - update table contents via an SPI call to UPDATE WHERE <column> IS NULL
>
> Sorry, I haven't read the spec, but what happens when there is a default
> value already and it's not NULL? Are tuples where column = default
> updated? Are tuples where column IS NULL updated?
We're talking about add column. Since it's a new column, there will
never be a default and all entries are NULL in PostgreSQL.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2003-06-19 14:30:30 | Re: add column .. default |
Previous Message | Tom Lane | 2003-06-19 14:12:49 | Re: add column .. default |