| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add column .. default |
| Date: | 2003-06-19 13:52:14 |
| Message-ID: | 1056030733.39060.10.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2003-06-19 at 09:40, Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)ca> writes:
> > Anyway, I suppose you have indirectly confirmed that user triggers, etc.
> > should NOT fire on for the data update. I didn't see anything in the
> > spec that said one way or the other.
>
> Actually, I didn't mean to take a position one way or the other. You
> could certainly argue that they should fire ...
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
The where clause would avoid issues with inherited data being
overwritten when the child tables are updated.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-06-19 14:03:13 | Re: add column .. default |
| Previous Message | Enke, Michael | 2003-06-19 13:40:37 | again: Bug #943: Server-Encoding from EUC_TW to UTF-8 doesn'twork |