|
Well, then a view is what the doctor
ordered.
1. rename table CUSTOMERS to
CUSTOMERS_A
2. create view CUSTOMERS select * from CUSTOMERS_A
UNION ALL CUSTOMERS_B;
If you do not want to show the duplicates in these
tables, make the UNION ALL just UNION.
HTH.
Arup
----- Original Message -----
Sent: Wednesday, July 16, 2003 12:14
AM
Subject: Re: Transparent database objects
after merging
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" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/16/2003 11:59 AM
Please respond to ORACLE-L
|
To:
Multiple recipients of list ORACLE-L
<[EMAIL PROTECTED]>
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: [EMAIL PROTECTED]
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,
|
