Skip site navigation (1) Skip section navigation (2)

Re: Changes to functions and triggers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain)
Cc: hackers(at)PostgreSQL(dot)org
Subject: Re: Changes to functions and triggers
Date: 2000-06-20 19:42:15
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
darcy(at)druid(dot)net (D'Arcy J.M. Cain) writes:
>> You sure you didn't fall into the same old trap of you-must-create-
>> the-trigger-after-the-function?  If you drop and recreate the function,
>> it has a new OID, so you have to drop and recreate the trigger because
>> it links to the function by OID.

> Positive.  I dropped both then did the above in the order shown.

Hm.  Is the OID shown in the error message the correct OID for your
trigger function, or not?  (Try "select oid,* from pg_proc where
proname = 'make_date'", maybe also "select * from pg_proc where
oid = 24224")

There are trigger examples in the regress tests that are hardly
different from your example, so the trigger feature is surely not
broken completely.  Maybe a platform-specific problem?  Which
version were you running again, exactly, and what configuration
options?  BTW, do the regress tests pass for you?

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Brook MilliganDate: 2000-06-20 20:01:47
Subject: table permissions and referential integrity
Previous:From: D'Arcy J.M. CainDate: 2000-06-20 19:33:33
Subject: Re: Changes to functions and triggers

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group