Re: FOREIGN KEY migration of syntax, help needed - Mailing list pgsql-general

From Mike Haberman
Subject Re: FOREIGN KEY migration of syntax, help needed
Date
Msg-id 20070731203456.GA44839@ncsa.uiuc.edu
Whole thread Raw
In response to Re: FOREIGN KEY migration of syntax, help needed  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thank you for the quick response.

   If all my old constraints are NOT DEFERRABLE INITIALLY IMMEDIATE
    does that mean I don't have to worry about the deferrable keyword?

   mike


On Tue, Jul 31, 2007 at 04:00:59PM -0400, Tom Lane wrote:
> Mike Haberman <mikeh@ncsa.uiuc.edu> writes:
> >    Will the following take care of all three statements?
>
> >    ALTER TABLE ONLY assettype
> >    ADD CONSTRAINT at_fk_1 FOREIGN KEY (pid) REFERENCES assettype(id)
> >    ON UPDATE CASCADE ON DELETE CASCADE;
>
> Yes, there are three or so triggers under the hood of any FOREIGN KEY
> constraint.
>
>             regards, tom lane

--
-----------------------------------------------------------------------
Mike Haberman
Senior Software/Network Research Engineer
National Center for Supercomputing Applications
217.244.9370
-----------------------------------------------------------------------

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: continue in plpgsql 7.4
Next
From: Ralph Smith
Date:
Subject: Re: Auto Starting +/or Shutdown on OS X