]
Gail Badner reassigned HHH-6210:
--------------------------------
Assignee: Adam Warski
Adam, please assign as appropriate.
Thanks,
Gail
ValidityAuditStrategy doesn't support a numeric column for the
revision end timestamp
-------------------------------------------------------------------------------------
Key: HHH-6210
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6210
Project: Hibernate Core
Issue Type: Bug
Components: envers
Affects Versions: 3.6.3
Environment: MySQL 5.1.55
Reporter: Nikita D
Assignee: Adam Warski
The revision timestamp of the revision entity (the field annotated with
@RevisionTimestamp) can be stored into a BIGINT column on MySQL. This allows having
millisecond precision on MySQL (see
http://bugs.mysql.com/bug.php?id=8523).
ValidityAuditStrategy additionally stores a revision end timestamp. The problem is that
it doesn't allow using a BIGINT column for this timestamp (see ValidityAuditStrategy
line 162).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: