From: | "Davor J(dot)" <DavorJ(at)live(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Inheritance and trigger/FK propagation |
Date: | 2010-07-27 08:36:16 |
Message-ID: | i2m5s8$gci$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
""Karsten Hilbert"" <Karsten(dot)Hilbert(at)gmx(dot)net> wrote in message
news:20100719182027(dot)123920(at)gmx(dot)net(dot)(dot)(dot)
>> On Thu, Jul 15, 2010 at 4:05 AM, Davor J. <DavorJ(at)live(dot)com> 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.
>>
>> Do you want your trigger that redirects insert on parent table to the
>> proper child table should run on child tables too?
>
> Well, inheritance is not used for partitioning ONLY. So, yes, for *my*
> use cases I would appreciate being able to tell triggers defined on
> parent tables to run on child tables when an insert/update/delete
> happens on a child table. (We use inheritance for auditing and for
> data aggregation.)
>
> But since I am not in a position to code the necessary infrastructure
> I won't complain about the status quo.
>
> Karsten
>
For me Vick's question just proves that inheritance in relational databases
is a complex issue. It shows that trigger propagation is not always desired,
contrary to what I believed.
But I also have to concur with Karsten.
Regards,
Davor
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2010-07-27 09:22:38 | Re: Converting BYTEA from/to BIGINT |
Previous Message | Davor J. | 2010-07-27 08:33:19 | Re: Inheritance and trigger/FK propagation |