3 ms·
Mysql closed out a long-standing one in January of this year: https://bugs.mysql.com/bug.php?id=12654 https://bugs.mysql.com/bug.php?id=12654
by tyingq 5y ago
Mysql closed out a long-standing one in January of this year:
https://bugs.mysql.com/bug.php?id=12654 https://bugs.mysql.com/bug.php?id=12654
- mackal 5y agoI was just trying to find that bug report to comment on it, should have just read the comments XD
- tyingq 5y agoWhat's kind of funny is that there seems to be a time related bug with the comments on the bug report page. All the timestamps look like [22 Dec 2021 9:43], except the last one, apparently made in 2022, which has a time of 20:22, and the year is missing: [3 Jan 20:22] Maybe it's intentional that the year is omitted for current year, and just a coincidence that the time is 20:22?
- bombcar 5y agoIt's likely the case, but it also goes to show why "cutesy" timestamps are annoying - even the "a few seconds ago" type you get.
- coffeedan 5y agoNow if only they would fix TIMESTAMP: https://dev.mysql.com/worklog/task/?id=1872 https://dev.mysql.com/worklog/task/?id=1872