| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | Alvaro Herrera <alvherre(at)atentus(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP COLUMN misbehaviour with multiple inheritance |
| Date: | 2002-09-24 23:13:18 |
| Message-ID: | 25388.1032909198@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers Postg토토 사이트 순위SQL |
Hannu Krosing <hannu(at)tm(dot)ee> writes:
> 1) --------------------------------
> create table p1 (f1 int, g1 int);
> create table p2 (f1 int, h1 int);
> create table c () inherits(p1, p2);
> drop column p2.f1; -- this DROP is in fact implicitly ONLY
Surely not? At least, I don't see why it should be thought of that way.
There's always a difference between DROP and DROP ONLY.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-24 23:15:41 | Re: Default privileges for 7.3 |
| Previous Message | Alvaro Herrera | 2002-09-24 23:05:18 | pg_dump and inherited attributes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-24 23:15:41 | Re: Default privileges for 7.3 |
| Previous Message | Hannu Krosing | 2002-09-24 22:29:34 | Re: DROP COLUMN misbehaviour with multiple inheritance |