Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4626

Timestamp truncated when converted to string with explicit calendar

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.5.3.0
    • Fix Version/s: 10.5.3.2, 10.6.2.4, 10.7.1.1
    • Component/s: SQL
    • Labels:
      None
    • Bug behavior facts:
      Wrong query result

      Description

      When setting the value of a VARCHAR parameter with setTimestamp() the timestamp is truncated to microsecond resolution if a calendar is specified. Nanosecond resolution is preserved when a calendar is not specified. These two methods should behave the same way. Since Derby supports nanosecond resolution, the timestamps should not be truncated.

        Attachments

        1. test.diff
          2 kB
          Knut Anders Hatlen
        2. TimestampToVarchar.java
          1 kB
          Knut Anders Hatlen

          Issue Links

            Activity

              People

              • Assignee:
                nirmal Nirmal Fernando
                Reporter:
                knutanders Knut Anders Hatlen
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: