pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: pgsql General List <pgsql-general@postgresql.org>
Subject: Re: Inheritance vs child tables (Was Domains)
Date: 02 Aug 2003 16:50:33 -0500
Message-ID: <1059861033.24817.57.camel@haggis> (raw)
In-Reply-To: <20030802140600.G99004@zoraida.natserv.net>
References: <20030801075335.D51229-100000@megazone.bigpanda.com>
	<60vfthl6q6.fsf@dev6.int.libertyrms.info>
	<16388.1059756693@sss.pgh.pa.us>
	<20030801131642.Q93127@zoraida.natserv.net>
	<1059782193.22384.85.camel@haggis>
	<20030802140600.G99004@zoraida.natserv.net>

On Sat, 2003-08-02 at 13:22, Francisco J Reyes wrote:
> On Fri, 1 Aug 2003, Ron Johnson wrote:
> 
> > On Fri, 2003-08-01 at 12:26, Francisco J Reyes wrote:
> > > On Fri, 1 Aug 2003, Tom Lane wrote:
> > [snip]
> > >  Currently I used inheritance to enforce the consitency
> > > since a good number of fields needed to be common among the tables AND the
> > > inheritted tables are basically a supperset of the data, so some times I
> > > would want to access the inheritted tables and other times the parent/main
> > > table.
> >
> > Isn't this when you'd really want child tables, instead?
> 
> 
> I think both ways can accomplish the same (if not very simmilar
> functionality), however I find using inherittance easier.
> Not really sure about efficiency though.
> 
> A simple example of the type of design I am planning to do would be:
> 
> Table A
> Userid
> date entered
> last changed
> 
> 
> Table B inherited from A(additional fields)
> person name
> birthday
> 
> Table C inherited from A(additional fields)
> book
> isbn
> comment
> 
> I plan to keep track of how many records a user has so with inherittance
> it's easy to do this. I can count for the user in Table A and find out how
> many records he/she has or I can count in each of the inheritted tables
> and see how many there are for that particular table.
> 
> Inheritance makes it easier to see everything for a userid or just a
> particular type of records.

But isn't this what LEFT OUTER JOIN is for?

Attached is a zip of the sql and results of what I mean.

Plain inner joins or LOJ with "WHERE {B|C}.whatever IS NOT NULL"
also pare things dawn.

Of course, just yesterday, in a post on -general or -performance,
I read that LEFT OUTER JOIN isn't particularly efficient in PG.

Also, wouldn't it be odd to have a userid without a name?  So,
why isn't table_b combined with table_a?  But all circumstances
are different, I guess...

-- 
+-----------------------------------------------------------------+
| Ron Johnson, Jr.        Home: ron.l.johnson@cox.net             |
| Jefferson, LA  USA                                              |
|                                                                 |
| "I'm not a vegetarian because I love animals, I'm a vegetarian  |
|  because I hate vegetables!"                                    |
|    unknown                                                      |
+-----------------------------------------------------------------+

Attachments:

  oj_example.zip (application/zip, 2.5K) download

view thread (3+ messages)  latest in thread

Message-ID: <1059861033.24817.57.camel@haggis>
Permalink:  ../1059861033.24817.57.camel@haggis/
Also on:    postgresql.org/message-id/1059861033.24817.57.camel@haggis

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: ron.l.johnson@cox.net, pgsql-general@postgresql.org
  Subject: Re: Inheritance vs child tables (Was Domains)
  In-Reply-To: <1059861033.24817.57.camel@haggis>
  References: <20030801075335.D51229-100000@megazone.bigpanda.com> <60vfthl6q6.fsf@dev6.int.libertyrms.info> <16388.1059756693@sss.pgh.pa.us> <20030801131642.Q93127@zoraida.natserv.net> <1059782193.22384.85.camel@haggis> <20030802140600.G99004@zoraida.natserv.net> <1059861033.24817.57.camel@haggis>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox