Uploaded image for project: 'OpenJPA'
  1. OpenJPA
  2. OPENJPA-1480

time zone info lost when using timestamp field

    XMLWordPrintableJSON

    Details

    • 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
    • Fix Version/s: None
    • Component/s: jdbc
    • Labels:
      None
    • Environment:
      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

        1. 1280-1.2.x.patch
          0.7 kB
          B.J. Reed
        2. OPENJPA-1480-TestCalendarField.patch
          1 kB
          B.J. Reed
        3. TestTimeZone.java
          11 kB
          B.J. Reed
        4. TZDataModel.java
          1 kB
          B.J. Reed

          Issue Links

            Activity

              People

              • Assignee:
                mikedd Michael Dick
                Reporter:
                bjreed B.J. Reed
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: