Re: INSTEAD OF trigger on VIEWs

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: "Jan B(dot)" <jan(at)monso(dot)de>
Cc: --= Tono =-- <tonodarmodjo(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: INSTEAD OF trigger on VIEWs
Date: 2005-05-23 14:46:26
Message-ID: 4291ECC2.2000508@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan B. 2005-05-23 15:01:12 Re: INSTEAD OF trigger on VIEWs
Previous Message Jan B. 2005-05-23 14:37:18 Re: INSTEAD OF trigger on VIEWs