| From: | "Dan Langille" <dan(at)langille(dot)org> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 7.4 - TODO : alter table drop foreign key |
| Date: | 2002-12-05 17:41:29 |
| Message-ID: | 3DEF4979.30970.6B688D5@localhost |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5 Dec 2002 at 9:31, Stephan Szabo wrote:
> When we talk about ALTER TABLE ADD FOREIGN KEY we're being imprecise, so
> I think that might be why we're talking past each other here.
>
> Technically the syntax in question is:
> ALTER TABLE <table> ADD <table constraint definition>
> where CONSTRAINT <name> is an optional leading clause in a table
> constraint definition. ADD FOREIGN KEY is a shorthand for a foreign key
> constraint (technically unnamed).
Understood.
What about allowing a named foreign key? I haven't checked the RFCs
> Thus you can also say things like:
> ALTER TABLE <table> ADD CONSTRAINT blah CHECK (foo!=0);
> to make a named check constraint.
Understood.
--
Dan Langille : http://www.langille.org/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2002-12-05 17:51:26 | Re: 7.4 - TODO : alter table drop foreign key |
| Previous Message | Stephan Szabo | 2002-12-05 17:31:15 | Re: 7.4 - TODO : alter table drop foreign key |