[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3710) Add Valid Time support

[jason shi (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34019#action_34019 ] 

jason shi commented on HHH-3710:
--------------------------------

hi,Anderson Teymeny
The simple valid time solution can't really solve your problems,because there is a reverse opertation at day 4.
To solve your problem,we need to introduce version tree concept(like SVN) into valid time solution. 
Every reverse opertion will create a new branch version.
The valid time + version tree solution require a master entity,for example: a version tree is only for an "Order" entity and it's sub entities.
There are some schema changes to orginal revison table design:
1. Revision table:
	-Revision Id (Key)
	-Master Entity Name (limit the revision tree to a special master entity)
	-Master Entity ID
	-Pre Revision Id (to create a version tree for current master entity)
	-IsActive (only active revision can has the valid time field, the reversed revision can't has valid time field)
	-Valid Time Business
2. Entity revision table (XXX_AUD tables)
	-Revision ID
	-Revision Type (new,update delete)
	-Start Valid Time  (included)
	-End Valid Time  (not included)
	-IsActive (reversed or not)



> Add Valid Time support
> ----------------------
>
>                 Key: HHH-3710
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3710
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: envers
>    Affects Versions: 3.5.0.Beta-1
>            Reporter: jason shi
>
> The envers uses transaction time for revisions (REVTSTMP field in REVINFO table).
> For many enterprise application, the valid time is more important than the transaction time, especially for those tables require revisions.
> In the envers_seam_demo, there is a bi-temporal demo, it uses additional query conditions (filter by actualDate),
> It's too complex for us.
> hope  the valid time can be supported natively

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira