From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> |
Cc: | Terry Lee Tucker <terry(at)esc1(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dazed and Confused |
Date: | 2004-02-16 15:45:47 |
Message-ID: | 25856.1076946347@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> writes:
> I believe OPAQUE is deprecated, and the return type of TRIGGER should be used.
Correct.
> 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"
Right, there is a narrow hack in CREATE TRIGGER that does that to allow
loading of existing dump scripts. But I think what Terry is trying to
do is modify an existing trigger function with
CREATE OR REPLACE trigfunc() RETURNS OPAQUE AS ...
and the system won't (and shouldn't) let him change the function return
type back to OPAQUE.
The only answer is to replace OPAQUE by TRIGGER in your function
scripts.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | C G | 2004-02-16 15:46:10 | Inputting columns of data |
Previous Message | Tom Lane | 2004-02-16 15:41:42 | Re: tsearch2: restoring problem |