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

Re: function return type for triggers in postgresql 8.0 rc2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "PEDRO LOPEZ" <p(dot)lopez(at)bresnan(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: function return type for triggers in postgresql 8.0 rc2
Date: 2004-12-30 00:17:24
Message-ID: 19420.1104365844@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"PEDRO LOPEZ" <p(dot)lopez(at)bresnan(dot)net> writes:
> after struggling with 'function not defined errors', and unable to see what 
> was wrong I redefined the function as:

> CREATE OR REPLACE FUNCTION currentstatus_dtrig() RETURNS opaque AS
> ...

> and got the message to the effect of 'redefining return type as trigger',

Yup.

> This is strange, AFAICT I followed the documentation setting up the trigger 
> and functions (correct parameter signature and return type).

It's been a long time (at least since 7.3) since the documentation
recommended using OPAQUE for anything.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2004-12-30 00:20:05
Subject: Re: BUG #1364: using field names or table names with blanks
Previous:From: Tom LaneDate: 2004-12-30 00:08:16
Subject: Re: plperl and pgport

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