Re: Oracle Synonyms & TableOwner Qualifier

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
>
>
>
Received on Fri Jun 18 1999 - 07:50:12 CDT