pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Re: [QUESTIONS] Inheriting Triggers
2+ messages / 2 participants
[nested] [flat]

* Re: [QUESTIONS] Inheriting Triggers
@ 1998-03-18 19:06  Peter T Mount <postgresdev@maidast.demon.co.uk>
  0 siblings, 0 replies; 2+ messages in thread

From: Peter T Mount @ 1998-03-18 19:06 UTC (permalink / raw)
  To: David Harvey-George <DavidH@uk.quza.com>; +Cc: 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 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





^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: [HACKERS] Re: [QUESTIONS] Inheriting Triggers
@ 1998-03-19 18:50  Maurice Gittens <mgittens@gits.nl>
  0 siblings, 0 replies; 2+ messages in thread

From: Maurice Gittens @ 1998-03-19 18:50 UTC (permalink / raw)
  To: Peter T Mount <postgresdev@maidast.demon.co.uk>; David Harvey-George <DavidH@uk.quza.com>; +Cc: 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




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~1998-03-19 18:50 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-03-18 19:06 Re: [QUESTIONS] Inheriting Triggers Peter T Mount <postgresdev@maidast.demon.co.uk>
1998-03-19 18:50 Re: [HACKERS] Re: [QUESTIONS] Inheriting Triggers Maurice Gittens <mgittens@gits.nl>

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