Re: Inheritance Semantics

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Mark Butler <butlerm(at)middle(dot)net>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Inheritance Semantics
Date: 2001-04-10 03:00:57
Message-ID: 200104100300.XAA08743@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

> 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Jaruwan Laongmal 2001-04-10 08:14:32 problem with copy command
Previous Message Roberto Mello 2001-04-10 02:40:57 Re: Sorting and then...