[CONC-168] string conversion of timestamps is broken Created: 2016-03-23  Updated: 2016-03-24  Resolved: 2016-03-24

Status: Closed
Project: MariaDB Connector/C
Component/s: None
Affects Version/s: 3.0.0, 2.2.0
Fix Version/s: 2.2.3, 3.0.1

Type: Bug Priority: Major
Reporter: Patrick Huesmann Assignee: Georg Richter
Resolution: Fixed Votes: 0
Labels: None
Environment:

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

 Comments   
Comment by Georg Richter [ 2016-03-24 ]

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

Generated at Thu Feb 08 03:03:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.