| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Dan Langille <dan(at)langille(dot)org>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 7.4 - TODO : alter table drop foreign key |
| Date: | 2002-12-05 20:10:22 |
| Message-ID: | 1039119022.71320.2.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2002-12-05 at 14:52, Christopher Kings-Lynne wrote:
> > > > Thanks. I guess I should rename my thread to 7.4 - TODO : allow
> > > > constraint names when using the "ALTER TABLE <table> ADD FOREIGN KEY"
> > > > syntax.
> > >
> > > You can do that now.
> > >
> > > ALTER TABLE <table> ADD CONSTRAINT <const> FOREIGN KEY ....
> >
> > That I know. That syntax is radically different from that proposed.
>
> Isn't it identical? The CONSTRAINT <const> is SQL standard optional clause
> for all commands that add constraints.
Not to mention the same as the CREATE TABLE syntax for constraints that
we already have.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-12-05 20:12:49 | Re: 7.3 pg_relcheck oddness |
| Previous Message | Christopher Kings-Lynne | 2002-12-05 20:09:06 | Re: 7.4 - TODO : alter table drop foreign key |