[OPENJPA-1480] time zone info lost when using timestamp field

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.2.3, 1.3.0, 2.0.0-M3, 2.0.0-beta
• Component/s: jdbc
• Environment: at least DB2, Derby, Sybase
• Assignee: Michael Dick
• Reporter: Barrett Jay Reed
• Created: 22/Jan/10 19:05
• Updated: 23/Jul/10 20:41
• Resolved: 23/Jul/10 20:41

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)

Issue Links

• is related to: OPENJPA-322 Timezone on the Calendar object lost in proxying