| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Rod Taylor <rbt(at)rbt(dot)ca> |
| 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:05:27 |
| Message-ID: | 20030619140527.GA13976@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
Y dijo Dios: "Que sea Satanás, para que la gente no me culpe de todo a mí."
"Y que hayan abogados, para que la gente no culpe de todo a Satanás"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-06-19 14:06:03 | Re: [Fwd: [GENERAL] [CYGWIN] Problems compiling PostgreSQL 7.3.3-1 under Win98] |
| Previous Message | Peter Eisentraut | 2003-06-19 14:03:13 | Re: add column .. default |