In our environment, we have three logical schemas in one database. Since all of these schemas are accessed from the same session factory and data source, we need to include the schema attribute in our hibernate mapping files. We would like to be able to create new sandbox environments by just adding new schemas in the same database. The problem, however, is that the schema names are already hard coded in the hibernate mapping files. Is it possible to change the values of the schema attributes at runtime?

Thanks.

-karl



Hibernate version: 3.05

Name and version of the database you are using: UDB 8.2

You can do it with
configuration.setProperty( "hibernate.default_schema",value)

see API for Configuration class

I don't think hibernate.default_schema would help me in this case since we have three different schemas for one session factory.

ste schema in *hbm.xml file or create 3 sessionFactory's for 3 schemas

We already set the schema in the hbm.xml file. The issue is we want to override this setting at runtime in places like dev and qa. The hibernate mappings are contained within the actual jars. We want to be able to move from dev to qa to prod without rebuilding these jars.



Three separate session factories would work, but I think it might be somewhat inefficient. We really only need one session factory since there is only one database.

Thanks.

-karl

How do you resolve in another application ?

you can change schema in class definition, define session factory ant what yet

if you have one program (one JVM) and three schemas create sessionfactory, but If you want production and db set property schema in your program (no in *.cfg.xml) then call

Here's a suggestion that might be a bit of extra work on your part.

When you configure your Hibernate session, rather than list all of your *.hbm.xml files in your Hibernate config file, you could load them manually using Configuration.addDocument(Document hbm);

Just before you add the hbm file, you could manipulate the table="schema1.MY_TABLE" attribute of each class element to, say, turn it into, say, "sandbox_schema1.MY_TABLE".

Since this would only happen at one time (Hibernate config time), it wouldn't really affect the runtime performance, but it'd probably be a slightly annoying amount of code.

I think this is an excellent idea.

Thanks!

-karl

it is easier manipulate with every *hbm.xml than with one *cfg.xml and Configuration
Congratulations.Go ahaed.

I cannot set this in the *cfg.xml since I have only one session factory for three schemas. I understand i could have a session factory per schema, but at this point it's too big of a change for our project.

You set *cfg.xml without default schema and in HibernateUtil (or what ever for SessionFactory) next :


your SchemaProperty is one from your schemas.You can make 3 *cfg.xml with your 3 schemas and call with this :


You can change any parameter in Configuration see chapter 4.1 in documentation (Programmatic configuration)

I think you are missing the point of snpesnpe's post. Don't put any schema in the hbms. Then you can set the default_schema at runtime through the Configuration and point to any schema you want.

Setting schema in mapping file (hbm) is bad idea general .Don't do it, if isn't necessary

I think you're missing the point of kbaum's post: there are three schemas in place in the production environment, and another three schemas in the sandbox environment.

Either kbaum needs three session factories per application instance (and that might have impacts on joins) or zie has to specify which hbms have which schemas.

yes, kbaum can change every *hbm.xml on runtime or remove schema from *hbm.xml once and change schema in configuration - hardcoded schema name will make problem always