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

[Wayne Straughn]

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-----
From: laura pena [mailto:[EMAIL PROTECTED]
Sent: Monday, February 24, 2003 12:29 PM
To: Multiple recipients of list ORACLE-L
Subject: Using fully qualified table_name.database_object in application 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! Tax Center - forms, calculators, tips, and more