2010/12/7 Gauthier, Dave <dave.gauth...@intel.com>

> I think aliasing non-table/view was mixed by Tom, but just as FYI, aliasing
> column names would be very helpful in my apps. Aliasing "last_name",
> "lastname", "surname" together in a people table for example.  We have many
> design sites that have identical data concepts but with different names for
> the same thing.  It would be nice to just equate these names in the DB
> instead of in perl wrappers around sql calls.
>
Interesting, how will you maintain synonyms in a many databases ?
IMO it is more simple to make abstraction level at the application side
in one place rather than create synonyms in different databases.


>
> -----Original Message-----
> From: pgsql-general-ow...@postgresql.org [mailto:
> pgsql-general-ow...@postgresql.org] On Behalf Of Andy Colson
> Sent: Monday, December 06, 2010 2:57 PM
> To: j...@commandprompt.com
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Do we want SYNONYMS?
>
> On 12/6/2010 1:31 PM, Joshua D. Drake wrote:
> > Hey -general,
> >
> > Command Prompt is currently considering writing a patch to provide
> > synonyms to PostgreSQL. Is this something the community is interested
> > in? Do we have use cases for it? MSSQL, DB2 and Oracle support them.
> >
> > Reference thread:
> >
> > http://archives.postgresql.org/pgsql-hackers/2010-11/msg02043.php
> >
> > Joshua D. Drake
>
> I dont understand the need for it.  Dont view's do the exact same thing
> (plus even more)?  What does a synonym offer that a view does not?
>
> And perusing the thread, I see it might cause all name and operator
> lookups to be slower?  (I didnt read all of it though)
>
> I'm gonna have to go:  -1
>
> -Andy
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>



-- 
// Dmitriy.

Reply via email to