wow.. Thank you.
mike
On Wed, Aug 01, 2007 at 10:31:16AM +0200, Dimitri Fontaine wrote:
> Le mardi 31 juillet 2007, Mike Haberman a ?crit?:
> >My old database has the old-style FOREIGN KEY syntax:
>
> I've had this very same transition to make on a database here, and
> successfully used a
Le mardi 31 juillet 2007, Mike Haberman a écrit :
>My old database has the old-style FOREIGN KEY syntax:
I've had this very same transition to make on a database here, and
successfully used adddepend:
http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/adddepends/adddepends/
It has been moved out
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 <[EMAIL PROTECTED]> writes:
> >
Mike Haberman <[EMAIL PROTECTED]> 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
Hi,
Quick question:
My old database has the old-style FOREIGN KEY syntax:
CREATE CONSTRAINT TRIGGER ""
AFTER INSERT OR UPDATE ON assettype
FROM assettype
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_check_ins"('', 'assettype',
'assettype'
