Design/Connection question ?

rajoos2004 · **Joined:** Mon Mar 08, 2004 5:22 pm **Posts:** 35

I have two questions:
1] I have two db instances on the same machines and i need to SELECT
ONE VIEW from each instance.
ex: machne1:masterf and machine2:masterfx
How do i configure that in hibernate.properties & keep them alive
through out the transaction ?

Keeping the both instances intact

Please help in the following scneario....

2] VIEW [PARENT called PLACE] has the following fileds
--------------------------------------------------
ID [UNIQUE]
NAME

VIEW [CHILD called PERSON] has the following fileds
--------------------------------------------------
AUCTION-ID[Can be compared against ID of the PARENT]
FIRSTNAME
LASTNAME
All the above fields are one composite key[COMPOSITE-ID]

CHILD component is working fine with COMPOSITE-ID
using HIBERNATE.

How do i relate both PARENT and CHILD ? What kind of mapping ?

Thanks for the help.

rajoos2004 · **Joined:** Mon Mar 08, 2004 5:22 pm **Posts:** 35

can someone answer this please

christian · **Posted:** Tue Mar 23, 2004 11:15 am

Your question doesn't make much sense. Hibernate uses two different SessionFactories, one for each database. There is no relationship in between, both use a distinct set of mappings and instances at runtime.

rajoos2004 · **Joined:** Mon Mar 08, 2004 5:22 pm **Posts:** 35

That is what i wanted to know. Does it make sense or not ?
Thank you for you logical explanation.

christian · **Posted:** Tue Mar 23, 2004 11:51 am

It's just the way Hibernate deals with multiple databases, i.e. there is no relationship between a JDBC connection to an Oracle database and another JDBC connection to a PostgreSQL database. I don't understand what you are trying to do with your views, however, so we might talk about different things.

rajoos2004 · **Joined:** Mon Mar 08, 2004 5:22 pm **Posts:** 35

I have the parent view on one instance[test area] and child on another[production area]. Once i could complete the relation [with mappings etc], the db team wants to create parent view on production too. Now i understand it is not right, since i cant make relation with two different instances. Your explanation helped me to express myself strongly to the db team. I will ask them to create the parent view also on the production. Now this seems confortable to me since i have some explanation for the problem.