[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-4540) Allow the revision timestamp to be a Date

[Adam Warski (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Warski resolved HHH-4540.
------------------------------

       Resolution: Fixed
    Fix Version/s: 3.5

> Allow the revision timestamp to be a Date
> -----------------------------------------
>
>                 Key: HHH-4540
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4540
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: envers
>            Reporter: Nicolas Rougé
>            Assignee: Adam Warski
>            Priority: Minor
>             Fix For: 3.5
>
>         Attachments: envers-timestamp.patch
>
>
> The revision timestamp, annotated with @RevisionTimestamp, can only be a long value, that is stored directly in the database. If someone want to query directly the database to get audit information between two dates, he has to convert the dates into long, and that conversion is not native on most of the databases.
> The attached patch allows you to define the revision timestamp as a Date (java.util or java.sql), so it is stored as a real date in the database.

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