> Could someone (Chris Mead?) post an update on the status of fixing
> PostgreSQL's inheritance semantics in the following ways:
>
> Has a decision been made to implementing true inheritance via INHERITS or an
> alternative keyword?
>
> By true inheritance, I mean first and foremost that any query on a super-class
> should query *all members* of that class by default regardless of which table
> they are stored in. Any other behavior violates the very natural expectation
> that a table called "PERSON" actually implements the class of all persons.
>
7.1 does that already.
> Second, for performance reasons, there needs to be a way for an index on a
> parent class attribute to be shared by all the tables that implement or
> inherit from that parent class. This is also necessary to enforce unique
> constraints on all members of a class.
That is on the TODO list, so I think we want it to happen.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
