Skip site navigation (1) Skip section navigation (2)

Re: Another proposal for table synonyms

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Alexey Klyukin <alexk(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Another proposal for table synonyms
Date: 2010-12-01 20:39:38
Message-ID: 1291235978.20631.3110.camel@jd-desktop (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, 2010-12-01 at 12:13 -0800, Josh Berkus wrote:
> > Well, porting applications from other database systems that support synonyms
> > (i.e. Oracle, DB2, SQL Server).
> 
> SQL Server supports synonyms?  If it's not Oracle-only, it's a more
> powerful argument to have the feature.

Oracle, DB2 and MSSQL support Synonyms.

> I'd love to hear from someone at EDB: how are you dealing with synonym
> name collisions right now?

I think the way we deal with that is the way PostgreSQL deals with it.
Unique names per search path.

> > Is this the feature the community would benefit from? We can consider adding
> > column synonyms if we won't hardwire synonyms to pg_class objects.

Column synonyms don't exist as far as I can tell (at least in Oracle)[1]

> 
> So, I don't support your idea of having a completely separate catalog.
> Sorry.

Yeah we have been talking about this internally and it seems (at least
to me) that the 85% solution in pg_class that supports
tables/views/sequences is best.

I posted to the Oracle list asking how many of them use Synonyms and
they are definitely a used feature.

JD

1. http://www.freelists.org/post/oracle-l/Synonyms

-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt


In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2010-12-01 20:46:00
Subject: Re: Another proposal for table synonyms
Previous:From: Jeff DavisDate: 2010-12-01 20:31:27
Subject: Re: crash-safe visibility map, take three

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group