openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Leung (JIRA)" <>
Subject [jira] Created: (OPENJPA-443) Calendar Objects are loaded with the current milliseconds
Date Thu, 15 Nov 2007 18:19:42 GMT
Calendar Objects are loaded with the current milliseconds

                 Key: OPENJPA-443
             Project: OpenJPA
          Issue Type: Bug
    Affects Versions: 1.1.0
         Environment: java full version "1.6.0_03-b05", fedora 7, OpenJPA 1.1.0 snapshot from
Nov 14, 2007, mysql  Ver 14.12 Distrib 5.0.45, for pc-linux-gnu (i686) using readline 5.0
            Reporter: Ted Leung

if you load an object which contains a Calendar object that has been persisted as date and
time (in the case of mysql that's without milliseconds, just  : DATETIME of format	'0000-00-00
00:00:00') the milliseconds are not 0-ed out.

as an example I loaded the same identical object twice one right after the other and I did
a Calendar. getTimeInMillis(). The results were 


I think 1195149779000 should have been the result. Right now it appears the millis were populated
from the current time of the query, I did print a System.currentTimeMillis and it the millis
seemed to match.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message