Re: PostgreSQL Inheritance and column mapping - Mailing list pgsql-general

From Tom Lane
Subject Re: PostgreSQL Inheritance and column mapping
Date
Msg-id 25921.1412258435@sss.pgh.pa.us
Whole thread Raw
In response to PostgreSQL Inheritance and column mapping  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
Responses Re: PostgreSQL Inheritance and column mapping  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-general
Achilleas Mantzios <achill@matrix.gatewaynet.com> writes:
> Was there ever any discussion.thought about being able to follow a non-strict by name
> column mapping between inherited tables and father tables?

No.  You could use a view with UNION ALL perhaps.

(The subtext here is that past discussion of inheritance has generally
focused on *eliminating* differences between parent and child tables, so
as to make query planning and execution faster/simpler.  That is, when the
discussion doesn't consist of somebody wanting to get rid of inheritance
altogether.  I think the enthusiasm for supporting even-less-compatible
child tables will be not distinguishable from zero.)

            regards, tom lane


pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: PostgreSQL Inheritance and column mapping
Next
From: Adam Brusselback
Date:
Subject: Re: table versioning approach (not auditing)