From: Maurice Gittens <mgittens@gits.nl>
To: Peter T Mount <postgresdev@maidast.demon.co.uk>
To: David Harvey-George <DavidH@uk.quza.com>
Cc: pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Re: [QUESTIONS] Inheriting Triggers
Date: Thu, 19 Mar 1998 19:50:24 +0100
Message-ID: <006901bd5367$e098f760$fcf3b2c2@caleb..gits.nl> (raw)
>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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: mgittens@gits.nl, postgresdev@maidast.demon.co.uk, DavidH@uk.quza.com
Subject: Re: [HACKERS] Re: [QUESTIONS] Inheriting Triggers
In-Reply-To: <006901bd5367$e098f760$fcf3b2c2@caleb..gits.nl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox