Re: [HACKERS] Re: [QUESTIONS] Inheriting Triggers - Mailing list pgsql-hackers

From Maurice Gittens
Subject Re: [HACKERS] Re: [QUESTIONS] Inheriting Triggers
Date
Msg-id 006901bd5367$e098f760$fcf3b2c2@caleb..gits.nl
Whole thread Raw
In response to [HACKERS] Re: [QUESTIONS] Inheriting Triggers  (Peter T Mount <postgresdev@maidast.demon.co.uk>)
List pgsql-hackers

>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


pgsql-hackers by date:

Previous
From: Peter T Mount
Date:
Subject: [HACKERS] Re: [QUESTIONS] Inheriting Triggers
Next
From: dg@illustra.com (David Gould)
Date:
Subject: Re: [HACKERS] tables >2GB