Bug #9271
closedInvalid DateTime/timestamp conversion in MySQL backend
100%
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
RS Updated by Roel Standaert almost 5 years ago
- Target version set to 4.7.0
KD Updated by Korneel Dumon over 4 years ago
- Assignee set to Korneel Dumon
KD Updated by Korneel Dumon over 4 years ago
- Status changed from New to InProgress
KD Updated by Korneel Dumon over 4 years ago
- Status changed from InProgress to Review
- Assignee deleted (
Korneel Dumon)
RS Updated by Roel Standaert over 4 years ago
- Status changed from Review to Implemented @Emweb
- Assignee set to Korneel Dumon
RS Updated by Roel Standaert over 4 years ago
- % Done changed from 0 to 100
RS Updated by Roel Standaert over 4 years ago
- Status changed from Implemented @Emweb to Resolved
RS Updated by Roel Standaert over 4 years ago
- Status changed from Resolved to Closed