The view will always have to have the schema qualification without a
synonym:
select from y.view_name.
I use roles, synonyms and stored procedures extensively in my application
and the combination has worked well so far. Is there a reason in your case
for not using synonyms?
Darlene
Suzy Vordos
When session is altered to the schema that owns the object, schema
qualification isn't needed. Our reason for eliminating the use of
public/private synonyms (where possible) is from a performance point of
view on the library cache. Steve Adams explains it best
http://www.ixora.com.au.
Alter
Thanks for the info. I knew you had to have a good reason.
Suzy Vordos wrote:
When session is altered to the schema that owns the object, schema
qualification isn't needed. Our reason for eliminating the use of
public/private synonyms (where possible) is from a performance point of
view on the
Just for your knowledge there is small bug that I reported to Oracle and
it's with development now.
It's simply when user1 does alter session set current schema to user2 ---
the default temp tablespace for user2 becomes effective for user1 during the
session.
regards,
Waleed
-Original
Good info, thanks. Guess it's not the only bug with current_schema.
Found info on Metalink indicating that alter current_schema then
accessing views via PL/SQL is another possible bug being investigated.
Whew, haven't totally lost my mind.
Which brings us back to Darlene's point of
