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

Home -> Community -> Usenet -> c.d.o.misc -> Re: Oracle Synonyms & TableOwner Qualifier

Re: Oracle Synonyms & TableOwner Qualifier

From: Thomas Kyte <tkyte_at_us.oracle.com>
Date: Fri, 18 Jun 1999 14:14:00 GMT
Message-ID: <3773540b.8706979@newshost.us.oracle.com>


A copy of this was sent to "Hank Riehl" <hankr_at_skillview.com> (if that email address didn't require changing) On Fri, 18 Jun 1999 10:04:57 -0400, you wrote:

>Since every User belongs to one-and-only-one app-specific Role, can I create
>private synonyms attached to the 8 Roles (whose privileges are granted to
>our app's schema only)?
>

nope, roles cannot create synonyms. synonyms are either private to a schema (a user account) or public (globally visiable).

>Many Thanks... Hank
>
>
>Peter Laursen wrote in message <01beb991$f8def3b0$2c289a0a_at_apollo>...
>>You can create private synonyms instead of public.
>>
>>You must create private synonyms for every user - since you might not know
>>every user beforehand you could make a procedure, that runs as the
>>schemaowner, and that creates the private synonyms for the calling user.
>>Remember the schemaowner must have the 'create any synonym' priv.
>>
>>Peter
>>
>>
>>Hank Riehl <hankr_at_skillview.com> skrev i artiklen
>><7kdbeg$7nv_at_news-central.tiac.net>...
>>> Our app (currently at PowerBuilder 6.5) has been deployed on a variety of
>>> backends,
>>> including SQL Svr, Syabse & Oracle.
>>>
>>> For Oracle sites, we create public synonyms for every table name (35 or
>>so
>>> tables) to eliminate the need for qualified reference; i.e.
>>> Create public synonym dept for tableowner.dept
>>> so that any user may simply run sql against table dept without need to
>>> reference tableowner.
>>>
>>> A new customer has indicated that these synonyms are unacceptable to
>>them.
>>> They are afraid of naming conflicts with other tables in other schemas in
>>> the instance.
>>>
>>> Does anyone have any ideas as to how to get around this? Our app uses
>>> embedded SQL as well as PowerBuilder Datawindows and the embedded SQL is
>>all
>>> written as
>>> unqualified.
>>>
>>> Any help here greatly appreciated.
>>>
>>> Hank
>>>
>>>
>>>
>

--
See http://govt.us.oracle.com/~tkyte/ for my columns 'Digging-in to Oracle8i'... Current article is "Fine Grained Access Control", added June 8'th  

Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation Received on Fri Jun 18 1999 - 09:14:00 CDT

Original text of this message

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