From: | <mallah(at)trade-india(dot)com> |
---|---|
To: | <reetz(at)usco(dot)de> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Dropping Foreign Key without recreating table |
Date: | 2002-11-24 14:12:04 |
Message-ID: | 57142.203.145.129.4.1038147124.squirrel@mail.trade-india.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Oops disregard my prev reply,
"RI_ConstraintTrigger_17195" is a trigger not contraint so u must in 7.2.1 do
DROP TRIGGER "RI_ConstraintTrigger_17195" on mytable ;
in 7.3 foreign key constraints on tables have name.
so you need not drop underlying triggers like in 721 but can use command to
drop the contraint which u are attempting now like
alter table mytable drop constraint "NAME OF THE FKEY CONSTRAINT" restrict ;
cheers
mallah.
> I wanted to change a foreign key to be deferrable (db version 7.2.1). During table creation I
> didn't specify a constraint name for the foreign key.
> "\d" shows a trigger RI_ConstraintTrigger_17195, however when I'm trying to "alter table
> mytable drop constraint RI_ConstraintTrigger_17195 restrict" I'm getting the error "constraint
> does not exist.
> What am I doing wrong here? Or is there another simple solution to switch foreign keys to be
> deferrable?
>
> Regards
>
> Egon
>
>
>
> ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off
> all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
-----------------------------------------
Get your free web based email at trade-india.com.
"India's Leading B2B eMarketplace.!"
http://www.trade-india.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Egon Reetz | 2002-11-24 15:37:29 | Re: Dropping Foreign Key without recreating table |
Previous Message | mallah | 2002-11-24 14:05:48 | Re: Dropping Foreign Key without recreating table |