25 Apr
2022
25 Apr
'22
2:07 p.m.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27253 --- Comment #21 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- (In reply to Julian Maurice from comment #20)
(In reply to Marcel de Rooy from comment #17)
So I would propose to switch to UNIXTIME(1). Note that I would consider this a bug in SQL.
It's weird that '1970-01-01 00:00:00' is not a valid timestamp but it's not really a bug IMO. MySQL documentation says that:
The TIMESTAMP data type is used for values that contain both date and time parts. TIMESTAMP has a range of '1970-01-01 00:00:01' UTC to '2038-01-19 03:14:07' UTC.
Ok no bug, inconsistency then :) -- You are receiving this mail because: You are watching all bug changes.