[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3572?page=c...
]
Brian Cunningham commented on HHH-3572:
---------------------------------------
Has there been any progress with this issue?
I am using Hibernate Envers in a large reservation system that is being re-written based
on a legacy system.
The old versioning mechanism effectively had 8 revision groups. If we had a similar option
in Hibernate Envers it would make the migration much simpler.
Using one revision entity also means that the revision id will grow very large and could
also become a source of a bottleneck.
Create versioned entities groups
--------------------------------
Key: HHH-3572
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3572
Project: Hibernate Core
Issue Type: New Feature
Components: envers
Reporter: Adam Warski
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136878
Each group would have its own versions table.
This could speed up the system when there are a lot of versioned entities, as the
versions tables would be less contested. However, if two versioned entities are connected
by a (versioned) relation, they would have to be in the same group. So groups could
minimally be strongly connected components of the relations graphs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira