From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | "Adam Rich" <adam(dot)r(at)sbcglobal(dot)net> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: altering foreign keys |
Date: | 2008-01-22 19:27:23 |
Message-ID: | B9EE63BE-EF77-4977-AA86-BE8FC23E5C3D@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jan 22, 2008, at 1:11 PM, Adam Rich wrote:
> In my database, I have a core table that nearly all other tables
> key against. Now I need to adjust all of those foreign keys to
> add a "on update cascade" action. Is there a way to alter the
> existing keys? (it didn't jump out at me in the manual)
>
> If not, is there a serious issue preventing this feature?
>
> If I have to drop and re-create all of the foreign keys, is it
> possible to wrap the whole operation in a transaction without
> risking invalid inserts in the referring tables? (I come from
> an Oracle background, where DDL causes an implicit commit)
DDL in Postgres is transactional so your second option will work just
fine.
Erik Jones
DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma Jr | 2008-01-22 19:33:54 | Re: altering foreign keys |
Previous Message | Gevik Babakhani | 2008-01-22 19:20:30 | PostgreSQL professionals group at LinkedIn.com |