To improve performance, I have two classes that are the same in every way but used in completely different scenarios, so I would like to split the tables for faster querying.

However I'm not sure how this works using Spring's Hibernate Template. So two questions,

1) Is entity names what I should be looking at to split them,

2) How can I load or save an object to the correct table, since those methods take the Class as an argument?

If you are using Hibernate Annotations, you would do the following.



After that, Hibernate will always know which table to access when you create instances of, or query for, SubClassA or SubClassB. It's that simple!

I'm still a little confused because in your example you are persisting subclasses, in my scenario the two classes are exactly the same, just a very reusable object that I would prefer to be saved in different tables.

I see. Well I've not used this myself but you could look into using @Embeddable entities. As far as I know you can only override column names but you might be able to work out a solution.

My solution could still work though. Both the subclasses are still instances of the super class, and your business logic code can treat them identically by assigning them to a variable of class TopLevel.

Though you say your two classes are the same, they are not really as far as hibernate is concerned as their persistance strategy needs to be different.

I think I found the solution, I can use entity-name to map the same class to a different table, and I can use the method save(String entityName, Object object) to persist the object. Thanks for your suggestions

Hello. You solution with entity-name is clearly discussed in "Java persistence with Hibernate". But does anybody know how to do this using annotations?