Re: INSTEAD OF trigger on VIEWs - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: INSTEAD OF trigger on VIEWs
Date
Msg-id 4291ECC2.2000508@familyhealth.com.au
Whole thread Raw
In response to Re: INSTEAD OF trigger on VIEWs  ("Jan B." <jan@monso.de>)
Responses Re: INSTEAD OF trigger on VIEWs  ("Jan B." <jan@monso.de>)
List pgsql-hackers
> I have a similar problem and already considered using RULEs, but I 
> encountered the problem, that I did not find any way to execute 
> procedures from RULEs without using SELECT, which creates always a 
> result set being passed to the application invoking the INSERT, UPDATE 
> or DELETE, even if the function is declared VOID. This is causing 
> trouble when using asynchronous command processing.

The solution then is for us to get around to implementing procedures, 
rather than functions, in PostgreSQL I think.

Chris


pgsql-hackers by date:

Previous
From: "Jan B."
Date:
Subject: Re: INSTEAD OF trigger on VIEWs
Next
From: "Jan B."
Date:
Subject: Re: INSTEAD OF trigger on VIEWs