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

From Jim Nasby
Subject Re: PostgreSQL Inheritance and column mapping
Date
Msg-id 542E0FDE.5020703@BlueTreble.com
Whole thread Raw
In response to Re: PostgreSQL Inheritance and column mapping  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PostgreSQL Inheritance and column mapping  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
List pgsql-general
On 10/2/14, 9:00 AM, Tom Lane wrote:
> 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.
FWIW, I've had some less than stellar results with that (admittedly, back on 8.4).

The other thing you could do is something like:

ALTER TABLE invoice_document RENAME TO invoice_document_raw;
ALTER TABLE invoice_document_raw RENAME invoice_no TO doc_no;
CREATE VIEW invoice_document AS
     SELECT ...
         , doc_no AS invoice_no
         , ...
     FROM invoice_document_raw
;

If you make that view writable then no one needs to know that you renamed the column in the underlying table.


pgsql-general by date:

Previous
From: Jim Nasby
Date:
Subject: Re: How to find greatest record before known values fast
Next
From: David G Johnston
Date:
Subject: Re: How to find greatest record before known values fast