Re: Table Inheritance Discussion

From: Curt Sampson <cjs(at)cynic(dot)net>
To: Don Baccus <dhogaza(at)pacifier(dot)com>
Cc: Jordan Henderson <jordan_henders(at)yahoo(dot)com>, Greg Copeland <greg(at)CopelandConsulting(dot)Net>, Hannu Krosing <hannu(at)tm(dot)ee>, PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Table Inheritance Discussion
Date: 2002-08-12 00:18:16
Message-ID: Pine.NEB.4.44.0208120912150.517-100000@angelic.cynic.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 11 Aug 2002, Don Baccus wrote:

> It's just type extensibility, really.

Yeah.

> As to why, again there's an efficiency argument, as I said earlier some
> joins can be avoided given PG's implementation of this feature:
> [TI and relational examples deleted]

What you gave is not the relational equivalant of the TI case as
implemented in postgres. Modeled correctly, you should be creating
a table for the child, and a view for the parent. Then you will
find that the relational definition uses or avoids joins exactly
where the TI definition does.

> There's also some error checking (using my inherited example):

The relational definition doesn't force the dependency, but as you
can delete and recreate the view at will without data loss, the
amount of safety is the same.

cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2002-08-12 01:07:20 Re: [GENERAL] workaround for lack of REPLACE() function
Previous Message Don Baccus 2002-08-11 23:59:48 Re: Table Inheritance Discussion