"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
- Original Message -
From:
Donald Fraser
To: [EMAIL PROTECTED]
Sent: Thursday, February 06, 2003 11:27
AM
Subject: [BUGS] Trigger function not
executing
OS: Redhat, kernel 2.4
PostgreSQL 7.3.1 on i686-pc-linux-gnu, compiled
by GCC 2.96
I have
"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
OS: Redhat, kernel 2.4
PostgreSQL 7.3.1 on i686-pc-linux-gnu, compiled by
GCC 2.96
I have a table that has two triggers functions
applied to it
1) CREATE TRIGGER trig_delete_user BEFORE DELETE ON
tbl_user FOR EACH ROW EXECUTE PROCEDURE delete_user();
2) CREATE TRIGGER trig_insert_sys_user
