Hello all,

this question references to Hibernate-Core 3.2.6.ga and Hibernate-Annotations 3.3.1.GA.
As stated in Java Persistence with Hibernate, chapter 3.4.1 p.147 et sqq., one can map a class several times using the entity-name tag.

I wonder if this somehow could be done using Hibernate-Annotations.

The goal my team mates and I want to reach is the following:

We're working on an application that connects to a legacy DB2 with a highly normalized table structure that must not be changed. We use the javax annotation @Table(name="VW98578") pointing to our tables.

So we created annotated entity classes using Hibernate tools reverse engineering and integrated everything using Spring 2.5. This works all fine :-)

But every table has two (!) mirror tables. One is for saving an historic record whenever an update or delete has occurred.
The other one is for storing temporary changes that remain temporary as long as the user doesn't explicitly submits her/his changes.

During the time the user works with the temporary table, the domain object is programmatically "locked". I.e. in a lookup table the entity's id is linked to the user's id.

My approach would now be to write Hibernate Interceptors, one for the historic data persistence, the other one to route the user's changes to the temporary views.

As we speak of of 100+ tables, I hesitate repeating the entities for the historical and temporary use.

The Hibernate reference and "Java Persistence (...)" show an intuitive way to reuse an entity class pointing to different tables using <entity-name> (see http://www.hibernate.org/hib_docs/reference/en/html/mapping-entityname.html).

Is there any way to get this configured using Hibernate Annotations? I couldn't find one, but would really appreciate any confirmation.

Or did somebody find a solution for a similar requirement?


Thanks for reading so far and kind regards from Europe, Germany, Berlin,

Karsten

Hello,
I have the same need and i dont find how to do this with Hibernate Annotations. If someone have a solution...

Thanks in advance,

Florent

Hi,

Have the same problem. Need to map a class to two tables (one for loading entities from existing data, another for storing new entities). Would appreciate any advice how to achieve this using JPA.

Regards,

As far as I know this can only be done when mapping with xml files.

Thanks, nordborg
I'm thinking about using em.createNativeQuery() in order to load entities from the "read-only" table.

I just ran into this same problem. I want to keep huge tables of events that happen on my website and have a new table each month in the same schema. Then I'll delete previous month's tables when i need to recover disk space.

I guess i could extend the base Event class once for each month (Event200901,Event200902, etc... ) , but I'd rather just tell the session what table name to use programaticly.

Did anyone find a solution besides switching to XML config files?

Thanks!

Matt

I ran into this thread in the forum in order to solve a similar problem. I have a Entity(Foo) table and a EntityHistory(FooHistory) table which gets loaded via some triggers.
I already have Foo mapped as a POJO, but now I also need to get FooHistory to work.

I plan to do the following....refactor and Push up to a new superclass

@MappedSuperclass
public abstract class AbstractFoo{
}

@Entity
public class Foo extends AbstractFoo {
}

@Entity
public class FooHistory extends AbstractFoo {
}

The solution you suggest works when one wants to work with 2 entities (Foo and FooHistory), however, the entity-name mechanism allows 2 mapping files to map 2 tables to ONE entity.

The rest of the code should not need to know which type of entity it is or if it does then there should be a field isArchived.

I am surprised that there is no annotation equivalent to entity-name.

Any updates since that time? Because i have directly same requirements.