[hibernate-issues] [Hibernate-JIRA] Created: (HHH-6210) ValidityAuditStrategy doesn't support a numeric column for the revision end timestamp

[Nikita D (JIRA)]

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


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.
-
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