Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Avoid a synonym

RE: Avoid a synonym

From: Natural Join B.V. <lex.de.haan_at_naturaljoin.nl>
Date: Wed, 3 Nov 2004 10:01:24 MET
Message-Id: <20041103090319.C451C36DF43@ha-smtp3.tiscali.nl>


check out Steve Adams' Ixora web site, search for the right keywords, and you'll find the explanation why public synonyms might cause trouble ...

Cheers,
Lex.

> It is not applicable in all situations but I have used a schema after_logon
> trigger which does an "alter session set current_schema=nnn" to avoid needing
> to create massive amounts of synonyms. Of course that only works if the user
> needs access to only objects in one schema.
> If you need to do that for very many users then a database after_logon
trigger
> may be easier to manage.
>
> Quoting DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>:
>
> > Nuno - Good point (as always). My reasons are as follows:
> >
> > 1. The application group has their strategy built around public synonyms.
> > 2. My boss likes public synonyms.
> > 3. As I recall, it was Jonathan Lewis who mentioned that public synonyms
> > could cause performance problems, and I have passed that along to my boss.
> > If anyone has a personal horror story to share, that might make an impact.
> >
>
> --
> regards
>
> Wolfgang Breitling
> Oracle 7,8,8i,9i OCP DBA
> Centrex Consulting Corporation
> www.centrexcc.com
>
> --
> http://www.freelists.org/webpage/oracle-l
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Nov 03 2004 - 02:58:54 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US