Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
1.2.3, 1.3.0, 2.0.0-M3, 2.0.0-beta
-
None
-
None
-
at least DB2, Derby, Sybase
Description
Looks like OpenJPA always gets the time stamp out at the time zone of the machine, not the time zone that was used originally.
The test case is putting in 2 TimeStamps
TTimestamp = 4-3-2004 21:0:0.0 (America/New_York)
TTimestampUTC = 4-4-2004 2:0:0.0 (UTC)
When OpenJPA gets those 2 timesamps back out of the database, they are
TTimestamp = 4-3-2004 21:0:0.0 (America/New_York)
TTimestampUTC = 4-3-2004 21:0:0.0 (America/New_York)
Attachments
Attachments
Issue Links
- is related to
-
OPENJPA-322 Timezone on the Calendar object lost in proxying
- Closed