"Donald Fraser" <[EMAIL PROTECTED]> writes:
> The BEFORE trigger function basically does nothing to modify the tuple in=
> any way. It does run a SELECT on the same table to do some routine checks =
> and before it can exit the function it sets a global flag to tell the AFTER=
> trigger functio
flag I have mentioned.
Have I misunderstood trigger functions or is this
a legitimate bug?
Regards
Donald Fraser
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Donald Fraser" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTEC
"Donald Fraser" <[EMAIL PROTECTED]> writes:
> If I run SQL such as DELETE FROM tbl_user WHERE id > '20'; and there is mor=
> e than one record that meets the condition (id > '20') then I get the follo=
> wing problem. The BEFORE trigger function is only being called on the first=
> record that is
