Re: [SQL] using constraint based paritioning to fix EAV type schemas? (view inheritance and constraints)

From: "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at>
To: "Andrew Hammond" <andrew(dot)george(dot)hammond(at)gmail(dot)com>, "Aaron Bono" <postgresql(at)aranya(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [SQL] using constraint based paritioning to fix EAV type schemas? (view inheritance and constraints)
Date: 2006-07-19 07:56:06
Message-ID: E1539E0ED7043848906A8FF995BDA579012B443A@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > I've seen a few EAV designs in practice. They've all been
problematic.
> > I'd like to have a better way of dealing with them. Which is why I'm

> > tentatively suggesting support for inheritance and constraints in
> > views. If there's some other way to achieve constraint based
exclusion
> > across a UNION of heterogenous tables, I'd love to hear it.
>
> If you do your own rules anyway, why can't you use
> inheritance and create the rules on the parent table and the
> constraints on the child tables ?

Ah, sorry, just saw that you want different column names in your
subtables.

Add me as another vote to extend the new constraint elimination to union
all views :-)

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas DCP SD 2006-07-19 08:00:36 Re: RESET CONNECTION?
Previous Message Zeugswetter Andreas DCP SD 2006-07-19 07:45:56 Re: [SQL] using constraint based paritioning to fix EAV type schemas? (view inheritance and constraints)