Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

TimestampType uses SimpleDateFormat, which does not include Timestamp nanoseconds

Description

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.

Activity

Brett MeyerJuly 8, 2014 at 3:10 PM

Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!

Brett MeyerApril 7, 2014 at 5:43 PM

In an effort to clean up, in bulk, tickets that are most likely out of date, we're transitioning all ORM 3 tickets to an "Awaiting Test Case" state. Please see http://in.relation.to/Bloggers/HibernateORMJIRAPoliciesAndCleanUpTactics for more information.

If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.

Thank you!

Holger SchildbergAugust 19, 2009 at 12:58 PM

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.

Rejected

Details

Assignee

Reporter

Components

Affects versions

Priority

Created August 3, 2007 at 10:10 PM
Updated July 8, 2014 at 3:10 PM
Resolved July 8, 2014 at 3:10 PM