Re: Prepping to break every past release... - Mailing list pgsql-hackers

From decibel
Subject Re: Prepping to break every past release...
Date
Msg-id DA8FADF8-D8D0-440B-8A54-60655E345A22@decibel.org
Whole thread Raw
In response to Re: Prepping to break every past release...  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Column Aliases WAS: Prepping to break every past release...  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Mar 4, 2009, at 5:07 PM, Josh Berkus wrote:
>> Back on that track, I'd like to see a facility whereby we could  
>> provide an alias (or synonym, to use a nearby subject) columns and  
>> other objects. That would help to overcome naming glitches without  
>> breaking things quite so much.
>
> Believe it or not, a large PostgreSQL user in LA just buttonholed  
> me about that particular feature idea at SCALE.  So it might be  
> generally useful as well -- not just for the system catalogs, bug  
> to allow businesses with long-use databases to manage change over  
> time.


Yes, I think aliasing (especially at the table level) would be handy.

And +1 on reviving newsysviews, but of course I'm biased... ;P
-- 
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Has anybody think about changing BLCKSZ to an option of initdb?
Next
From: decibel
Date:
Subject: Re: hstore improvements?