Re: Using fully qualified table_name.database_object in application code?

Consensus seems to be it isn't a good idea.

An alternative to public synonyms is a to included 'alter session set current_schema=<SCHEMA>' alter session set current_schema=scott

e.g. alter session set current_schema=scott

Jared

On Monday 24 February 2003 08:29, laura pena wrote:
> I would like to know if it is advocated to use fully qualified
> table_name.database objects in application code.
>
> Example would be schema.table_name in a PL/SQL code.
>
> I would like to know the Pros/Cons if there are any?
>
> Thanks in advance.
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Tax Center - forms, calculators, tips, and more

Content-Type: text/html; charset="us-ascii"; name="Attachment: 1"
Content-Transfer-Encoding: 7bit
Content-Description: 
----------------------------------------

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jared Still
  INET: jkstill_at_cybcon.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).