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

setTimestamp() methods don't agree on trailing zeros

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.7.1.1
    • Fix Version/s: 10.7.1.1
    • Component/s: SQL
    • Labels:
      None
    • Bug behavior facts:
      Embedded/Client difference

      Description

      With the statement

      VALUES CAST(? AS VARCHAR(29))

      PreparedStatement.setTimestamp(int,Timestamp) and PreparedStatement.setTimestamp(int,Timestamp,Calendar) don't agree on what to do with trailing zeros in the nanosecond component. The method that doesn't take a Calendar argument, removes trailing zeros. The method that takes a Calendar object appends zeros so that the nanosecond component always has nine digits. (Both methods have a special case when nanoseconds is zero, and they agree on adding just a single zero after the decimal point in that case.)

      The format used by PreparedStatement.setTimestamp(int,Timestamp) matches what java.sql.Timestamp.toString() returns (in fact, it uses Timestamp.toString() internally to produce the string representation), and I think it would be reasonable to use that format for both the methods.

        Attachments

        1. derby-4810-1a.diff
          4 kB
          Knut Anders Hatlen
        2. test.diff
          2 kB
          Knut Anders Hatlen

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: