Hello!

Here is the situation I have:
There are multiple legacy SQL Server databases with exactly the same structure. Each database holds data for a specific customer and this is how it's gonna be due to business requirements.
So, what I wanna do is, when user tries to log in, he/she should provide also the database name along with his/her credentials. Then I could pick up the proper SessionFactory for the database and use it to manage persistence.
Is it possible to do that via configuration or programatically (like adding mapped classes for each Factory configuration)?
Have anyone had a similar situation and what could be a good decision?
Btw, I would like to use Hibernate 3.x for that project.

Any ideas would be appreciated. Thank you.

Jana Parvanova

I believe it is possible.

Well you can have different session factories for different databases, and all your entities must be mapped in each session factory.

after login, use the proper session factory for each user to create proper session and the rest of the work is the same.

I believe it is possible.

Well you can have different session factories for different databases, and all your entities must be mapped in each session factory.

after login, choose the proper session factory for each user to create session and the rest of the work is the same.
--------------------
don't forget credits.

It is possible. For each database you would need a seperate Hibernate Configuration, pointing at a different DB. Each configuration would be it's own SessionFactory.

How you actually set it up can get complicated. Off the top of my head, I would just hardcode each configuration for each client, and depending on who logs in use the appropriate SessionFactory that is already in the JVM.

If there are too many clients you would probably have to devise some sort of SessionFactory pool, that creates a NEW SessionFactory if he is the only user hitting DB1. If another user logs on and needs DB1, the SessionFactory would already be there and he would take part in it. When no other users needs DB1, the SessionFactory would be destroyed (to save memory).

The main point to remember is that it's a 1-1-1 relationship of Configurations-SessionFactory-Database.

Thank you for the replies.
It was kinda what I imagined (building Session Factories when needed and adding mapped classes to them). I guess I should just give it a try.