Re: Selecting data from other user's schema: Best way to eliminate table owner?

The keyword PUBLIC provides access to a particular object within an instance to anyone able to connect to that instance. Setting a user's session to a single schema within an instance isn't quite the same thing, although it might be appropriate in some cases. However, I probably wouldn't characterize the ALTER SESSION command as an "undocumented feature".

John Garrott			Data Systems Coordinator
email jjgarrott_at_concentric.net	L.A. County Sheriff's Dept
				Data Systems Bureau
==========================================================

In article <01bc7827$b24427c0$b3570c26_at_systems-douglas>, douglas_at_yogananda-srf.org says...
>
>There is an undocumented feature that will do this:
> alter session set current_schema = xxxxx; (no quotes)
>
>Doug
>
>
>
>Thomas Greuter <grth1_at_zh.swissptt.ch> wrote in article
><01bc7655$d4537bf0$62d5bb8a_at_tzhi95>...
>> What is the best way of easy selecting data from an other user's schema?
>> ...
>> We used synonyms to break down the schema-barrier:
>> create public synonym PRODS for ABC_MGR.PRODS; (as system)
>> and all the TZHusers may do theirs selects without knowing about ABC_MGR.
>>
>> Q: Is this a common way in Oracle? If no, are there some other ways to
>> eliminate the table/schema owner we didn't see?
>
Received on Fri Jun 20 1997 - 00:00:00 CDT