Re: Inheritance and trigger/FK propagation

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: "Davor J(dot)" <DavorJ(at)live(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Inheritance and trigger/FK propagation
Date: 2010-07-15 09:23:08
Message-ID: 4C3ED37C.1070007@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 15/07/10 16:05, Davor J. wrote:
> It seems no secret that a child table will not fire a trigger defined on
> it's parent table. Various posts comment on this. But nowhere could I find a
> reason for this.

[snip]

> I read in the change logs of 8.4: "Force child tables to inherit CHECK
> constraints from parents (Alex Hunsaker, Nikhil Sontakke, Tom)." So why not
> with triggers and FK's?

My understanding is that it's mostly an implementation limitation. In
other words, rather than any fundamental reason why it should not be
done, the issue is that nobody has gone and implemented it, tested it,
and ironed out the quirks and corner cases yet.

--
Craig Ringer

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vincenzo Romano 2010-07-15 09:55:22 Inheritance efficiency
Previous Message Allan Kamau 2010-07-15 09:02:16 Re: Redundant database objects.