Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: [QUESTIONS] Inheriting Triggers

From: "Maurice Gittens" <mgittens(at)gits(dot)nl>
To: "Peter T Mount" <postgresdev(at)maidast(dot)demon(dot)co(dot)uk>, "David Harvey-George" <DavidH(at)uk(dot)quza(dot)com>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Re: [QUESTIONS] Inheriting Triggers
Date: 1998-03-19 18:50:24
Message-ID: 006901bd5367$e098f760$fcf3b2c2@caleb..gits.nl (view raw or flat)
Thread:
Lists: 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

Next:From: Bruce MomjianDate: 1998-03-19 19:47:10
Subject: Re: [HACKERS] Re: [PATCHES] patches for 6.2.1p6
Previous:From: Zeugswetter AndreasDate: 1998-03-19 18:04:18
Subject: Re: [HACKERS] varchar() vs char16 performance

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group