support for Assocations / Relations

[cgs.schaefer]

i have implemented several versions for history interceptors in the past and i am happy to find envers now. as for my exp. such a history table concept is easy as long as associations are not considered,

and i am not able to find something in the documentation about assocation/relation support currently or in the future ?

What for example can be done/or is supported when a person address is for example:  n:m.

A person can have multiple addesses, and an address may or may not be assigned to multiple persons.

thnks.

chris

[adamw]

Hello,

auditing relations (or associations) is one of the main features of Envers. You can find a detailed description on how Envers stores and retrieves data in the documentation. For many-to-many relations, you need a join table, and Envers creates a parallel audit join table.

Adam

[cgs.schaefer]

we read the dokumention here:

http://www.jboss.org/files/envers/docs/index.html

there is nothing in there how relations are handled or how mapping tables are handled.

thanks.

[adamw]

There's some information here:

http://www.jboss.org/files/envers/docs/index.html#tables

Relations aren't handled in any special way, just the id of the related entity is written to the audit table.

When you read an entity that has some relations, a special proxy is created that (lazily) for each such field, which reads the related entity at the given revision, using the same algorithm as reading an entity at a given revision using the AuditReader.

Adam