Project

General

Profile

Bug #9271

Invalid DateTime/timestamp conversion in MySQL backend

Added by Steven Köhler about 1 year ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
11/01/2021
Due date:
% Done:

100%

Estimated time:

Description

When examining a MySQL/MariaDB database I use in a Wt project I noticed that all timestamps, without a single exception, had the format YYYY-MM-DD HH:MM:SS.000 - the millisecond part was always exactly zero, although the original timestamps definitely had non-zero millisecond parts. The issue occurred when storing WDateTime as well as std::chrono::system_clock::time_point. It turned out that the culprit is an invalid conversion in the MySQL backend.

I fixed the underlying issues and created a pull request (https://github.com/emweb/wt/pull/180) some weeks ago, but it seems to have gotten unnoticed. The pull request contains a more detailed description of the issue/solution. It would be nice if you could take a look at it.

Best regards
Steven

#1

Updated by Roel Standaert about 1 year ago

  • Target version set to 4.7.0
#2

Updated by Korneel Dumon 12 months ago

  • Assignee set to Korneel Dumon
#3

Updated by Korneel Dumon 12 months ago

  • Status changed from New to InProgress
#4

Updated by Korneel Dumon 12 months ago

  • Status changed from InProgress to Review
  • Assignee deleted (Korneel Dumon)
#5

Updated by Roel Standaert 9 months ago

  • Status changed from Review to Implemented @Emweb
  • Assignee set to Korneel Dumon
#6

Updated by Roel Standaert 9 months ago

  • % Done changed from 0 to 100
#7

Updated by Roel Standaert 9 months ago

  • Status changed from Implemented @Emweb to Resolved
#8

Updated by Roel Standaert 9 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF