Re: INSTEAD OF trigger on VIEWs

Поиск
Список
Период
Сортировка
От Jan B.
Тема Re: INSTEAD OF trigger on VIEWs
Дата
Msg-id 4291F038.3040100@monso.de
обсуждение исходный текст
Ответ на Re: INSTEAD OF trigger on VIEWs  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Список 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 по дате отправления:

Предыдущее
От: Christopher Kings-Lynne
Дата:
Сообщение: Re: INSTEAD OF trigger on VIEWs
Следующее
От: --= Tono =--
Дата:
Сообщение: Re: INSTEAD OF trigger on VIEWs