[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2767) TimestampType uses SimpleDateFormat, which does not include Timestamp nanoseconds

[Holger Schildberg (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33816#action_33816 ] 

Holger Schildberg commented on HHH-2767:
----------------------------------------

This also affects the logging of the bind parameters when the log level on the category org.hibernate.type is set to TRACE - as no nanoseconds are displayed, this makes the logging nearly useless. Really annoying.

> TimestampType uses SimpleDateFormat, which does not include Timestamp nanoseconds
> ---------------------------------------------------------------------------------
>
>                 Key: HHH-2767
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2767
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.2.2
>         Environment: Hibernate 3.2.2
>            Reporter: Alan Krueger
>            Priority: Minor
>
> TimestampType uses SimpleDateFormat when storing the value as a string, which does not include java.sql.Timestamp's nanoseconds.  This appears to mean that auto-flushes see Timestamp fields changing value when using EntityType.DOM4J when there is a nanosecond component to the timestamp.

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