Rick(dot)Casey(at)colorado(dot)edu presumably uttered the following on 02/25/05 19:14:
> Yes, thank you, I corrected my function from statement level to row level.
> This did get rid of the error message. However, I still get no output from
> an OLD variable that should contain data: see the test variable in the
> simple case below.
> How else can I test OLD variables? This is the simplest test case I can
> think of. Any suggestions would be appreciated!
>>I think you have created a statement level trigger (If they existed in
>>7.4.7...) by not including FOR EACH ROW in your create statement. In
>>statement level triggers, there is no OLD or NEW.
>>>>>Rick Casey <rick(dot)casey(at)colorado(dot)edu> 02/24/05 1:22 PM >>>
>>I am trying to a simple thing: create a log history of deletes, and
>>updates; but which I am having trouble getting to work in PG 7.4.7
>>(under Debian Linux 2.6.8).
>>I have reduced my code to the following trivial case:
>>Here is the code that creates the delete trigger:
>>create trigger PEDIGREES_hist_del_trig
>>EXECUTE PROCEDURE logPedigreesDel();
>>Here is the trigger code: (famindid is an integer field in the Pedigrees
>>CREATE OR REPLACE FUNCTION logPedigreesDel() RETURNS TRIGGER AS '
>> test integer;
>> test := OLD.famindid;
>> RAISE EXCEPTION ''OLD.famindid = '', test;
>> return OLD;
>>' LANGUAGE plpgsql;
Need a place holder for your variable in your RAISE expression (like a
RAISE EXCEPTION ''OLD.famindid = %'', test;
btw, if you just want to see the variable without having your function
bail on you, try RAISE NOTICE ''OLD.famindid = %'', test;
In response to
pgsql-general by date
|Next:||From: Julian Scarfe||Date: 2005-02-27 10:58:16|
|Subject: Re: postgresql 8.0 advantages |
|Previous:||From: Christopher Browne||Date: 2005-02-27 02:12:54|
|Subject: Re: postgresql 8.0 advantages|