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

From: Wayne Straughn <Wayne.Straughn_at_blpc.com.bb>
Date: Mon, 24 Feb 2003 10:34:00 -0800
Message-ID: <F001.005570CA.20030224103400@fatcity.com>

One possible disadvantage is that your apps are then 'tied' to a particular schema... if you wanted to run them against another schema, you would have to go back and modify everything...  

To get around this:
You could create public synonyms pointing to a particular schema's tables so if a reason ever arose to switch schema you'd only have to modify one set of code... your public synonym script.  

Wayne Straughn

 -----Original Message-----
Sent: Monday, February 24, 2003 12:29 PM To: Multiple recipients of list ORACLE-L code?

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! <http://rd.yahoo.com/finance/mailtagline/*http://taxes.yahoo.com/> Tax Center - forms, calculators, tips, and more

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: Wayne Straughn
  INET: Wayne.Straughn_at_blpc.com.bb

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). Received on Mon Feb 24 2003 - 12:34:00 CST