Re: Dazed and Confused

Hi Robert,

I changed the return type from OPAQUE to TRIGGER and the trigger function
reloaded without any complaint. I suppoe that when I loaded this new version
(with the output from pg_dumpall) that the return type was automatically set
to TRIGGER? I couldn't understand the fact that the code initally loaded
without complaint, but now, upon trying to reload, I was getting an error
with the same code.

Anyway, thanks for the response...

On Monday 16 February 2004 07:58 am, Robert Creager saith:
> When grilled further on (Mon, 16 Feb 2004 07:39:25 -0500),
>
> Terry Lee Tucker <terry(at)esc1(dot)com> confessed:
> > as in, \i cust/cust_preupd_func.plsql, I get an error. The error is:
> > psql:logs/logs_preupd_func.plsql:132: ERROR: ProcedureCreate: cannot
> > change return type of existing function.
> > Use DROP FUNCTION first.
>
> Per the error message, execute DROP FUNCTION function_name( ) before trying
> to CREATE FUNCTION.
>
> I believe OPAQUE is deprecated, and the return type of TRIGGER should be
> used. But, I still have a trigger which I have not updated that is OPAQUE,
> and it loads just find after emitting:
>
> psql:dbTriggers.sql:33: WARNING: changing return type of function
> observations_trigger from "opaque" to "trigger"
>
> Cheers,
> Rob

--
Work: 1-336-372-6812
Cell: 1-336-363-4719
email: terry(at)esc1(dot)com