| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add column .. default |
| Date: | 2003-06-19 15:41:07 |
| Message-ID: | 1056037266.39060.48.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2003-06-19 at 15:00, Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)ca> writes:
> > Right now if the column exists in the child table, the add column is
> > rejected. I assume that will remain.
>
> Have you actually tried it?
I used different datatypes which, of course, was the wrong test.
When I update the values in t1 I need to ensure I only get data from t1
that has the new column NULL.
Constraints to be checked are still only the ones attached to the
altered table directly. A constraint on t1 only will not affect data on
t2.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jon Jensen | 2003-06-19 16:09:31 | Re: src/bin/scripts seems a bit of a misnomer now |
| Previous Message | Christian Plattner | 2003-06-19 15:16:10 | Access to transaction status |