[HACKERS] SELECTs inside of VIEWs (WAS: INSTEAD OF trigger on VIEWs)

I tried using SELECTs inside of RULEs, but as I already explained in this mail thread, the problem is, that a SELECT creates a result set, which can not be discarded in SQL. This makes trouble when using asynchronous command processing. I have tried to modify my application in order to get a w

Re: [HACKERS] INSTEAD OF trigger on VIEWs

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,

Re: [HACKERS] INSTEAD OF trigger on VIEWs

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 fun