On 7/28/2014 10:58 AM, Jan Nijtmans wrote:
2014-07-28 16:53 GMT+02:00 Richard Hipp <d...@sqlite.org>:
Better to keep the code simpler and just say that SQLite (and hence Fossil)
does not know about leap seconds.
If you can do that in two bytes .... ;-)
All your fix does is have the parser accept "60" as valid seconds field.
That's not very interesting. The interesting part is a) validating that
it actually *is* a valid timestamp (was there a leap second on that
particular day, hour and minute) and b) doing time arithmetic in a way
that is aware of leap seconds (e.g. datetime(t, '+1 minute') and
datetime(t, '+60 seconds') may have to produce different results,
depending on the value of t).
Combine that with the fact that there's no practical way to know exactly
when leap seconds are introduced, and you are faced with a large effort
for very little benefit (if any at all; an argument could be made that
leap seconds introduce more problems than they solve).
--
Igor Tandetnik
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
