[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5371?page=c...
]
Adam Warski commented on HHH-5371:
----------------------------------
Somehow I stopped receiving email notifications for the issue :/
Anyway, my main question about rationale was why is the timestamp held for the
end-revision, rather then the start-revision?
I can see two benefits of using the start-revision:
* it never changes - isn't that a requirement for partitioning?
* it is available in both audit strategies
Also, if the patch fixes some problems with the ValidityAS, I think it should be moved to
another issue and another commit.
Adam
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: Erik-Berndt Scheper
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