Uploaded image for project: 'MariaDB Connector/C'
  1. MariaDB Connector/C
  2. CONC-168

string conversion of timestamps is broken

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 3.0.0, 2.2.0
    • 2.2.3, 3.0.1
    • None
    • None
    • All OSes

    Description

      ps_fetch_datetime() does not work for DATETIME( n ) fields where n is between 1 and 5.

      for example, when DATETIME(3) is used for millisecond resolution, the current version sprintf()s the first 3 digits of the microsecond field, but this yields a wrong output, when there are leading zeroes (see examples below).

      Test values, type DATETIME(3):
      2016-03-09 07:51:49.000
      2016-03-09 07:51:49.001
      2016-03-09 07:51:49.010

      ps_fetch_datetime() output:
      2016-03-09 07:51:49
      2016-03-09 07:51:49.1000
      2016-03-09 07:51:49.10000

      See github pull requests for fixes:
      master: https://github.com/MariaDB/mariadb-connector-c/pull/17
      2.2.x: https://github.com/MariaDB/mariadb-connector-c/pull/16

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          patrickh Patrick Huesmann created issue -
          patrickh Patrick Huesmann made changes -
          Field Original Value New Value
          Description ps_fetch_datetime() does not work for DATETIME(n) fields where n is between 1 and 5.

          for example, when DATETIME(3) is used for millisecond resolution, the current version sprintf()s the first 3 digits of the microsecond field, but this yields a wrong output, when there are leading zeroes (see examples below).

          Test values, type DATETIME(3):
          2016-03-09 07:51:49.000
          2016-03-09 07:51:49.001
          2016-03-09 07:51:49.010

          ps_fetch_datetime() output:
          2016-03-09 07:51:49
          2016-03-09 07:51:49.1000
          2016-03-09 07:51:49.10000

          See github pull requests for fixes:
          master: https://github.com/MariaDB/mariadb-connector-c/pull/17
          2.2.x: https://github.com/MariaDB/mariadb-connector-c/pull/16           		ps_fetch_datetime() does not work for DATETIME( n ) fields where n is between 1 and 5.

          for example, when DATETIME(3) is used for millisecond resolution, the current version sprintf()s the first 3 digits of the microsecond field, but this yields a wrong output, when there are leading zeroes (see examples below).

          Test values, type DATETIME(3):
          2016-03-09 07:51:49.000
          2016-03-09 07:51:49.001
          2016-03-09 07:51:49.010

          ps_fetch_datetime() output:
          2016-03-09 07:51:49
          2016-03-09 07:51:49.1000
          2016-03-09 07:51:49.10000

          See github pull requests for fixes:
          master: https://github.com/MariaDB/mariadb-connector-c/pull/17
          2.2.x: https://github.com/MariaDB/mariadb-connector-c/pull/16
          georg Georg Richter added a comment -

          Fixed in commit 7bda45564f838f8a320efd8704eb2c8a15d975e2
          Thanks for reporting this bug and providing a patch

          georg Georg Richter added a comment - Fixed in commit 7bda45564f838f8a320efd8704eb2c8a15d975e2 Thanks for reporting this bug and providing a patch
          georg Georg Richter made changes -
          Fix Version/s 2.2.3 [ 21500 ]
          Fix Version/s 3.0.1 [ 21501 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          julien.fritsch Julien Fritsch made changes -
          Workflow MariaDB connectors [ 74642 ] MariaDB v4 [ 161012 ]

          People

            georg Georg Richter
            patrickh Patrick Huesmann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.