[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2767?page=c...
]
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira