Re: Transparent database objects after merging

From: <Ukrit.Kuprasit_at_allianz.com.sg>
Date: Wed, 16 Jul 2003 11:14:28 +0800
Message-Id: <25929.337928@fatcity.com>

This is a multipart message in MIME format. --=_alternative 0011CE3C48256D65_=
Content-Type: text/plain; charset="us-ascii"

Hello,

Sorry I might not give all the problem corectly. I need to access to both CUSTOMERS and also CUSTOMERS_B. Not just only one. If only one table, my head will not spin like this.
^__^
Ukrit K,

"Arup Nanda" <orarup_at_hotmail.com>
Sent by: ml-errors_at_fatcity.com
07/16/2003 11:59 AM
Please respond to ORACLE-L

        To:     Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
        cc: 
        Subject:        Re: Transparent database objects after merging

You can drop or rename CUSTOMERS to, say, CUSTOMERS_A, and then create synonym CUSTOMERS pointing to CUSTOMERS_B. Or rename CUSTOMERS_B to CUSTOMERS. HTH. Arup Nanda
----- Original Message -----
From: Ukrit.Kuprasit_at_allianz.com.sg
To: Multiple recipients of list ORACLE-L Sent: Tuesday, July 15, 2003 11:29 PM
Subject: Transparent database objects after merging

Hello Gurus,

I'm working merging 2 databases which have sane structure of database objects into one database. However, after merging, the business policies and regulations force us to have 2 set of database objects; for example :
Database A has CUSTOMERS table.
Database B has CUSTOMERS table.

After merging database A will have CUSTOMERS and CUSTOMERS_B (data from database B). I just wonder that is there any way that we don't need to change our script in forms and reports to point into a new table name but still can access to the data in the new table ( CUSTOMERS_B) not CUSTOMERS.
Thank you for any comment and suggestion. Ukrit K,

--=_alternative 0011CE3C48256D65_=
Content-Type: text/html; charset="us-ascii"

 Hello,
         Sorry I might not give all the problem corectly. I need to access to both CUSTOMERS and also CUSTOMERS_B. Not just only one. If only one table, my head will not spin like this.
 ^__^
 Ukrit K,
 
 
 
<table width=100%>
<tr valign=top>
<td>
<td>"Arup Nanda" <orarup_at_hotmail.com>
 Sent by: ml-errors_at_fatcity.com
07/16/2003 11:59 AM
 Please respond to ORACLE-L
 
<td>        
         To:        Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
         cc:        
         Subject:        Re: Transparent database objects after merging</table>
 
 
 You can drop or rename CUSTOMERS to, say, CUSTOMERS_A, and then create synonym CUSTOMERS pointing to CUSTOMERS_B. Or rename CUSTOMERS_B to CUSTOMERS.
  
 HTH.
  
 Arup Nanda
 ----- Original Message ----- 
 From: <a href=mailto:Ukrit.Kuprasit_at_allianz.com.sg>Ukrit.Kuprasit_at_allianz.com.sg</a> 
 To: <a href="mailto:ORACLE-L_at_fatcity.com">Multiple recipients of list ORACLE-L</a> 
 Sent: Tuesday, July 15, 2003 11:29 PM
 Subject: Transparent database objects after merging
 
 
Hello Gurus,        I'm working merging 2 databases which have sane structure of  database objects into one database. However, after merging, the business policies and regulations force us to have 2 set of database objects; for example : Database A has CUSTOMERS table. Database B has CUSTOMERS table. 
 
After merging database A will have CUSTOMERS and CUSTOMERS_B (data from database B). I just wonder that is there any way that we don't need to change our script in forms and reports to point into a new table name but still can access to the data in the new table ( CUSTOMERS_B) not CUSTOMERS. Thank you for any comment and suggestion. Ukrit K, Received on Tue Jul 15 2003 - 22:14:28 CDT