Re: [QUESTIONS] Inheriting Triggers
On Wed, 18 Mar 1998, David Harvey-George wrote:
I found that triggers don't get inherited... or rather the triggers
for the superclass don't get checked when inserting or updating rows
when enforcing referential intregrity. This is a bit of a pain as it
means I have to duplicate a lot of triggers. Any idea if this can be
fixed? Presumably this would mean 'fixing' to the TRIGGER handling
code to look up the inheritance stack calling the appropriate
triggers?Maybe like inheriting PRIMARY KEY attributes this is more of a
feature?
I did ask about this last weekend (while looking at some features for
JDBC). This looks like a similar problem.
--
Peter T Mount petermount@earthling.net or pmount@maidast.demon.co.uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk
Import Notes
Reply to msg id not found: cGB%a_%pQuza%lEXCHANGE01-980318173200Z-28810@exchange01.uk.quza.com
On Wed, 18 Mar 1998, David Harvey-George wrote:
I found that triggers don't get inherited... or rather the triggers
for the superclass don't get checked when inserting or updating rows
when enforcing referential intregrity. This is a bit of a pain as it
means I have to duplicate a lot of triggers. Any idea if this can be
fixed? Presumably this would mean 'fixing' to the TRIGGER handling
code to look up the inheritance stack calling the appropriate
triggers?Maybe like inheriting PRIMARY KEY attributes this is more of a
feature?
I'm glad that I'm not the only one who is of the opinion that inheritance is
needed for triggers and the like.
Regards,
Maurice
Import Notes
Resolved by subject fallback