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

Home -> Community -> Usenet -> c.d.o.server -> Re: Why PUBLIC SYNONYM is bad ?

Re: Why PUBLIC SYNONYM is bad ?

From: cava123 <cava123_at_noos.fr>
Date: Sun, 16 Jun 2002 16:55:19 +0200
Message-ID: <3D0CA6D7.215988DB@noos.fr>

Nuno Souto a écrit :

> In article <3D0BFE6D.5860BDDE_at_noos.fr>, you said (and I quote):
>
> > Our dba said that public synonym is very bad for performance and for
> > security to access data.
> > why ? (technical reasons please)
>
> Another example of "rules" and "examples" taken out-of-context suddenly
> becoming gospel.
>
> Public synonyms CAN be bad for performance. This doesn't mean that they
> ALWAYS must be. And this does NOT apply to private synonyms.
> >>> But that require more library_cache ?

> As for security, that is rubbish. Public or not, what governs access to
> tables pointed to by synonyms is the grant on the table. Nothing to do
> with the synonyms themselves.
> >>> what happen if there is a public synonym EMP for scott.emp (default
> TS=DSCOTT_1) and another shema scott2 in DSCOTT_1 create the same table ? I
> mean in the other shémas a different user may access to the wrong data ?
> For some good text stuff on public synonyms and their performance impact,
> see Steve Adam's site: www.ixora.com.au
> There is a section on newsletters and IIRC the synonym stuff is in one of
> them.
>
> --
> Cheers
> Nuno Souto
> nsouto_at_optushome.com.au.nospam
Received on Sun Jun 16 2002 - 09:55:19 CDT

Original text of this message

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