Bug Report
MySQL on Alpha Linux stores or appears to store incorrect 'time' and
'datetime' data. Inputting a value into a datetime field and then selecting
it out again will result in a datetime similar to 00-00-0000 00:01:85
yes, that is 85 seconds ). Similarly, time value get returned like
529::10::23, with very large hour values. 'date' fields do not appear to be
affected.
It does not appear to be an input parsing problem as 'INSERT INTO table
values ( now() )', using the internal now() function does not work either.
It does not appear to be in the display code either, as 'SELECT now()'
returns the correct time.
MySQL version is 3.22.25, which is a little old, but we are unable to
upgrade it at this time, and do not have another Alpha box, but I have
permission to make a shell account available if someone from TcX wants to
make a more in depth investigation.
No other field types appear to be affected, although I have not done a full
search, and there does not seem to be a data integrity test in the tests,
they all appear to be benchmarks. Apart from the actual problem, might it be
worth adding a data integrity test into the test suite, to pick up weird
situations like this one?
Adam Kennedy
Principal Systems Developer
NetRegistry Pty Ltd
