[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5371?page=c...
]
Erik-Berndt Scheper commented on HHH-5371:
------------------------------------------
Thanks for reviewing the initial patch!
I have attached two new patches which fixes the following issues:
1. Use of the end-revision-timestamp is optional, and by default *NOT* enabled.
2. Configuration of this functionaly is ruled by two new properties:
* org.hibernate.envers.audit_strategy_valid_time_store_revend_timestamp
Used to enable / disable end-revision-timestamp is optional (defaults to *false*)
* org.hibernate.envers.audit_strategy_valid_time_revend_timestamp_field_name
Used to determine the column nameend-revision-timestamp column (defaults to
*REVEND_TSTMP*)
3. I have created a new test class that verifies the behavior of the new
end-revision-timestamp column.
4. I have added documentation of the new properties (in a separate patch)
Add support for REVEND_TSTMP which will enable SQL table partitioning
by time
-----------------------------------------------------------------------------
Key: HHH-5371
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5371
Project: Hibernate Core
Issue Type: New Feature
Components: envers
Affects Versions: 3.6.0.Beta1
Reporter: Matthew B. Jones
Assignee: Adam Warski
Attachments: HHH-5371-revend_tstmp-documentation-20100908.patch,
HHH-5371-revend_tstmp-revised-20100908.patch, revend_tstmp.txt
There is strong desire to be able to purge old records out of a relational database by
using table partitioning. In order to partition a table, you need to partition it on a
column that exists within the table. So, in order to partition the _AUD tables by expired
time, the timestamp of REVEND must be present within the table.
--
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