ValidityAuditStrategy doesn't support a numeric column for the revision end timestamp

Description

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

Environment

MySQL 5.1.55

Assignee

Chris Cranford

Reporter

Nikita D

Fix versions

Labels

backPortable

None

Suitable for new contributors

None

Requires Release Note

Affirmative

backportDecision

None

Components

Affects versions

Priority

Minor
Configure