Re: Inheritance question - Mailing list pgsql-general

From Andrew Sullivan
Subject Re: Inheritance question
Date
Msg-id 20070530135242.GD16260@phlogiston.dyndns.org
Whole thread Raw
In response to Inheritance question  ("Raymond C. Rodgers" <rrodgers@bbnk.dhs.org>)
List pgsql-general
On Thu, May 24, 2007 at 04:44:53PM -0700, Raymond C. Rodgers wrote:
> The question, and point, is this: Is there an alternate way of
> accomplishing read and write functionality similar to what inheritance
> offers but allowing me to map the columns as I desire? The read only

It isn't clear from your question whether the data in the tables is
_the same_ in these cases.  If so, then you could have various child
tables inherit the parent, and the parent would be the largest of all
the tables (the child tables without the columns in question would
just have those columns null).  But in general, my impression is that
you don't want inheritance here.  What you probably want is better
normalization of your data on the way in.

A


--
Andrew Sullivan  | ajs@crankycanuck.ca
The fact that technology doesn't work is no bar to success in the marketplace.
        --Philip Greenspun

pgsql-general by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: postgres access - pg_hba.conf
Next
From: Andrew Sullivan
Date:
Subject: Re: 8.3