Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3A31E808832 for ; Mon, 9 Apr 2001 23:01:14 -0400 (EDT) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id XAA08743; Mon, 9 Apr 2001 23:00:57 -0400 (EDT) From: Bruce Momjian Message-Id: <200104100300.XAA08743@candle.pha.pa.us> Subject: Re: Inheritance Semantics In-Reply-To: <3AD2691C.35AD23F3@middle.net> "from Mark Butler at Apr 9, 2001 07:59:56 pm" To: Mark Butler Date: Mon, 9 Apr 2001 23:00:57 -0400 (EDT) CC: pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200104/131 X-Sequence-Number: 2478 > 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 pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026