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

From Jan B.
Subject Re: INSTEAD OF trigger on VIEWs
Date
Msg-id 4291F038.3040100@monso.de
Whole thread Raw
In response to Re: INSTEAD OF trigger on VIEWs  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
Christopher Kings-Lynne wrote:

>> 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
>
Yes, I think that this would be a good way to solve the problem, but is 
it planned to implement procedures in near future?
What about extending the SQL command set by an "INVOKE" command, which 
invokes a function and discards the result?

Jan Behrens


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: INSTEAD OF trigger on VIEWs
Next
From: --= Tono =--
Date:
Subject: Re: INSTEAD OF trigger on VIEWs