Can I map the same class to a different table at runtime? For example, can I map class Review to both REVIEW and REVIEW_2002 which have the same table structure depends on some condition?

We have an application which handles employee's annual review data. It has 3 year worth of data, and I am in the process of devising an archiving solution before the query gets too slow. The idea is to move the historical data to its own table, i.e. REVIEW_2000, REVIEW_2001, and REVIEW_2002. I have thought about using inheritance or interface to solve the mapping such as having Review2002 that inherits Review class. However, it requires creating new mapping class and duplicated mapping definition for each year. There must be a better way to handle this problem. Can anyone shed some light?

Thanks,
Barry

I searched through the forum and found a few other users tried to do a similiar thing, but couldn't find a definite answer or sample code. Here's what I came up after the research,



It is not working unfortunately. The table name was changed successfully, but the generated SQL still points to the old table name. It there cache somewhere that I need to invlidate/refresh?

Someone in the forum mentioned using custom persister for this requirement. Are there any examples that I can look into?

Thanks.

Did you rebuild your SessionFactory from the modified Configuration?

No, I didn't. I figured out that all the SQLs are cached once the SessionFactory is built. Anyway, changing the meta model like this will not serve my needs as it will affect other parts of the system. The goal is to change the query on the fly without altering the original mapping or the original mapping should be restored immediately, so other queries/updates to the main table are not affected. It looks like that I will have to go with creating multiple mappings and inherited classes for this requirement unless there's more natural mechanism than updating the mappings through Configuration.

Thanks,
Barry

You can have two SessionFactory instances.