Re: Re: CAST doesn't work - Mailing list pgsql-novice

From Joel Burton
Subject Re: Re: CAST doesn't work
Date
Msg-id Pine.LNX.4.21.0104232047590.2376-100000@olympus.scw.org
Whole thread Raw
In response to Re: Re: CAST doesn't work  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-novice
On Mon, 23 Apr 2001, Tom Lane wrote:

> Jason Davis <jdavis@tassie.net.au> writes:
> > Is it possible to remove a referential integrity trigger without dropping
> > tables? I tried to DROP TRIGGER using the name of the trigger created from
> > the foreign key clause when the table was created, without success (no such
> > trigger name).
>
> Were you careful about case sensitivity?  The RI trigger names are
> deliberately made mixed-case to reduce the odds of collision with user
> trigger names... but AFAIK you should be able to drop 'em if you quote
> 'em correctly.

(possibly, Jason, what you think is the trigger name isnt'.)

When your RI triggers are created by PostgreSQL, it chooses the trigger
name itself (what Tom is referring to, above).

The name *you* provide (via a "constraint xxxx references" clause) becomes
a different column, tgconstrname. Check *there* for your trigger name.

--
Joel Burton   <jburton@scw.org>
Director of Information Systems, Support Center of Washington


pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: CAST doesn't work
Next
From: Joel Burton
Date:
Subject: Re: BETWEEN clause