Re: Triggers not working - Mailing list pgsql-general

From Dale Harris
Subject Re: Triggers not working
Date
Msg-id 00bb01c91d30$5cd21f80$16765e80$@com.au
Whole thread Raw
In response to Re: Triggers not working  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I would have called the Entity table the parent table and not the child
table as the Account table inherits from Entity.  Therefore it appears that
the trigger only works on the table where the actual row was added/belongs
to.

It would be great if triggers on the parent table would work for any row
that appears there, even rows added via a child table.  It would mean that
any new table that inherits the parent table, in my case Entity, would
automatically have the global trigger I want enforced. Nice enhancement :)

Regards,

Dale Harris.


-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Tuesday, 23 September 2008 13:43
To: Dale Harris
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Triggers not working

"Dale Harris" <itsupport@jonkers.com.au> writes:
> The trigger trAccountUpdate got called, but why didn't the trigger
> trEntityUpdate get called?

Triggers only apply to the exact table they're declared on, not
to child tables.

It does seem like there might be some use-case for applying a trigger to
child tables too, but that's not how it works now.

            regards, tom lane


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Triggers not working
Next
From: Craig Ringer
Date:
Subject: Re: match an IP address