From: | Hannu Krosing <hannu(at)krosing(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 7.2 stuff |
Date: | 2002-02-25 04:39:51 |
Message-ID: | 1014611991.2172.3.camel@rh72.home.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2002-02-25 at 07:53, Tom Lane wrote:
> "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > * ALTER TABLE DROP PRIMARY KEY
> > - Done, will need review
> > * ALTER TABLE DROP UNIQUE
> > - Done, will need review
>
> > I'll dredge this up again if I can. All it does is add a standards
> > compliant alternative syntax for dropping those constraints. Tom - can you
> > just do this in the parser, like you did it for the ADD constraints???
>
> I don't foresee it falling out of other parser work, if that's what you
> mean. If you want it done in the parser you'll have to do it yourself.
>
> There are some semantic issues, eg: what does it mean to do ALTER TABLE
> DROP PRIMARY KEY in an inheritance hierarchy? Does every child lose its
> primary key (if any), even if it's not inherited from the parent?
Probably not as the primary key is currently not inherited when doing
create.
------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2002-02-25 04:43:27 | Re: 7.2 stuff |
Previous Message | Bruce Momjian | 2002-02-25 04:26:24 | Re: patch queue |