"Christopher Kings-Lynne" <chriskl@familyhealth.com.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?
I could see doing the "where's the primary key" lookup either at
execution time (separately for each table) or at parse time (lookup once
at the parent table) depending on which behavior you want.
regards, tom lane
