| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: DROP COLUMN misbehaviour with multiple inheritance |
| Date: | 2002-09-30 03:48:18 |
| Message-ID: | 14580.1033357698@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)atentus(dot)com> writes:
> I implemented "ADD ONLY" as a way to add the column only in the parent
> (all children should already have to column, errors if at least one
> doesn't or is different atttype), while "ADD" adds the column to
> children that don't have it and merges where already exist; it errors if
> children have different atttype etc.
I fail to see the value in such a distinction. The end state is the same
in both cases, no?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-30 03:53:59 | Re: [SQL] CURRENT_TIMESTAMP |
| Previous Message | Neil Conway | 2002-09-30 03:03:52 | Re: making use of large TLB pages |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-09-30 05:01:34 | Get constrrelid for fk constraints that lost it |
| Previous Message | Alvaro Herrera | 2002-09-29 19:05:01 | Re: DROP COLUMN misbehaviour with multiple inheritance |