Re: Re: CAST doesn't work

From: Joel Burton <jburton(at)scw(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jason Davis <jdavis(at)tassie(dot)net(dot)au>, pgsql-novice(at)postgresql(dot)org
Subject: Re: Re: CAST doesn't work
Date: 2001-04-24 00:50:06
Message-ID: Pine.LNX.4.21.0104232047590.2376-100000@olympus.scw.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-novice

On Mon, 23 Apr 2001, Tom Lane wrote:

> Jason Davis <jdavis(at)tassie(dot)net(dot)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(at)scw(dot)org>
Director of Information Systems, Support Center of Washington

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vince Vielhaber 2001-04-24 01:16:30 Re: [HACKERS] Re: Hardcopy docs available
Previous Message Tom Lane 2001-04-24 00:16:02 Re: Re: CAST doesn't work

Browse pgsql-novice by date

  From Date Subject
Next Message Paul Tomblin 2001-04-24 02:54:05 BETWEEN clause
Previous Message Tom Lane 2001-04-24 00:16:02 Re: Re: CAST doesn't work