| From: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Prepping to break every past release... |
| Date: | 2009-03-04 23:20:58 |
| Message-ID: | 63754043-7827-460D-8D7C-0BE7EEE4C74D@themactionfaction.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 4, 2009, at 6:07 PM, Josh Berkus wrote:
> Andrew,
>
>> 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.
Schema change is a strong motivator for applications to access the
database through views and functions only. A column with multiple
names would likely make it *more* painful to migrate schemata.
Cheers,
M
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dickson S. Guedes | 2009-03-05 00:02:14 | Re: cbrt() broken in AIX |
| Previous Message | Josh Berkus | 2009-03-04 23:12:45 | Re: Prepping to break every past release... |