[EMAIL PROTECTED] writes:
> is it somehow possible to create trigger functions directly in
> SQL language, w/o an procedural language ?
No.
> Why cant the return value of an function simply be ignored,
> instead of requiring the function to return void (which an sql
> function can't return) ?
I
Hi folks,
is it somehow possible to create trigger functions directly in
SQL language, w/o an procedural language ?
Why cant the return value of an function simply be ignored,
instead of requiring the function to return void (which an sql
function can't return) ?
cu
--
-
On Tue, Jun 17, 2003 at 11:49:44AM -0700, Josh Berkus wrote:
I also need something like that for my replication stuff:
When data from another node comes it, it should be written
directly to the tables, without any (unwanted) triggers firering.
On the other hand, in "normal" mode, also some mi
Tom Lane wrote:
Jan Wieck <[EMAIL PROTECTED]> writes:
Unfortunately, you're right. There is no way do distinguish in a trigger
or rule if a value in the new row did result from the UPDATE query or
from target list expansion with OLD values.
It would not be terribly hard to examine the original
