From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Linh Luong <linh(dot)luong(at)computalog(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: dropping constraints |
Date: | 2001-06-07 16:36:20 |
Message-ID: | Pine.BSF.4.21.0106070935490.21399-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
You probably need to make sure to double quote the tgname in your drops.
On Thu, 7 Jun 2001, Linh Luong wrote:
> Hi,
>
> Is there to drop a constraint when you add it separately with an alter
> statement.
>
> alter table failuretypecategory1 add constraint fk_failuretypecategory1
> FOREIGN KEY (failurecategory1id)
> REFERENCES failurecategory1 (id) ON UPDATE CASCADE ON DELETE CASCADE;
>
> I tried
> drop trigger <tgconstrname> on failurecategory1
> and
> drop trigger <tgconstrname> on failuretypecategory1
>
> and also
>
> drop trigger <tgname> on failurecategory1
> and
> drop trigger <tgname> on failuretypecategory1
>
>
> But it kept saying
> ERROR: DropTrigger: there is no trigger <tgname>/<tgconstrname> on
> relation failuretypecategory1
>
> What am I doing wrong.
>
> I tried dropping the table also and when I tried to delete from a table
> that it referenced above it gave the error that the table I just drop
> doesn't exist. Obviously because I just removed it but the constraint
> it still there..
From | Date | Subject | |
---|---|---|---|
Next Message | Clayton Cottingham aka drfrog | 2001-06-07 16:50:34 | Re: plperl |
Previous Message | Josh Berkus | 2001-06-07 15:53:21 | Re: behavior of ' = NULL' vs. MySQL vs. Standards |