| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 21:20:21 |
| Message-ID: | 1032902424.2820.40.camel@rh72.home.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Wed, 2002-09-25 at 04:13, Tom Lane wrote:
> 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.
What will be the difference in the user-visible schema ?
------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-24 21:33:57 | Re: contrib/earthdistance missing regression test files |
| Previous Message | Hannu Krosing | 2002-09-24 21:12:14 | Re: DROP COLUMN misbehaviour with multiple inheritance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-24 21:36:14 | Re: cleanup standard includes |
| Previous Message | Hannu Krosing | 2002-09-24 21:12:14 | Re: DROP COLUMN misbehaviour with multiple inheritance |