Can I create two different mappings to the same database table.

For example (we have a legacy system), I have a table with 100 columns. I want two different objects to represent different columns in the database.

I've read http://www.hibernate.org/41.html but it seems not a intuitive way to handle this (I don't want inheritance). I'm using 2.1.6. Will future versions (e.g Hibernate 3) handle this better?

Dino

You can have different mapping on the same table as long as you only load 1 row at the same time in the session.

Why is the cached object based on the table name and not on the class name?

Dino

There is no cahced object.
Think in a different way.
What if you have 2 instances representing the same row (and possibly the same column). Which one Hibernate will chose to win the race when you update both ?

I understand your response but it was a technique I used with TopLink. I basically had two or three type of objects (CoreInformation, DetailedInformation). I never liked lazy loading since if I had many one to ones then it would become inefficient to retrieve data.

In the the scenerio you described it would never happen since I wouldn't have overlap columns.

Even if I did have overlap columns, then I would evict from the cache the other representation so the next time it is retrieve it will grab the value from the database (I would never update both representation within the same session). Ibatis can do this as well via configuration.

Thanks

Dino