| From: | "Karsten Hilbert" <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Inheritance and trigger/FK propagation |
| Date: | 2010-07-19 18:20:27 |
| Message-ID: | 20100719182027.123920@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> 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
wiki.gnumed.de
--
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2010-07-19 19:16:48 | Re: Rescue data after power off |
| Previous Message | Scott Marlowe | 2010-07-19 18:19:47 | Re: Create table if not exists ... how ?? |