From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Adding Foreign Key Constraint To Existing Table |
Date: | 2011-07-01 21:42:08 |
Message-ID: | BANLkTim+uRVdaJf1ap_NXfKm3MM+9dPPcA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1 July 2011 22:00, Rich Shepard <rshepard(at)appl-ecosys(dot)com> wrote:
> I've examined the 9.0 manual page on alter table without seeing how to add
> a foreign key constraint to a column.
>
> I needed to make changes on a couple of existing tables which could be
> accomplished only by dropping the foreign key constraint. That, and changing
> the table structure, column names, and column types were successful. But, I
> am not seeing the proper syntax to add a foreign key constraint back to the
> two affected tables.
By the way, rather than dropping the foreign key then recreating it,
you could always do this:
ALTER TABLE tablename DISABLE TRIGGER ALL;
Then it would ignore the foreign key trigger and you could put in
mischievous values... but remember to enable it again (replace DISABLE
with ENABLE). You'll have to be a superuser to do it though.
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2011-07-01 22:04:44 | Re: Adding Foreign Key Constraint To Existing Table |
Previous Message | Rich Shepard | 2011-07-01 21:39:23 | Re: Adding Foreign Key Constraint To Existing Table |