2014-07-28 18:28 GMT+02:00 Igor Tandetnik <i...@tandetnik.org>:
> What do you mean "ignore"? Can you specify precisely what the semantics of
> such a timestamp should be, in all the date/time manipulation operations
> SQLite supports?
Just as julianday('2012-06-30T24:00:00') is exactly equal to
julianday('2012-07-01T00:00:00'), my proposal is that
julianday('2012-06-30T23:59:60') is handled as being
equal to this exact same timestamp. That's easiest to
implement changing only 2 bytes to SQLite's source code.
OK, OK, the documentation at <http://www.sqlite.org/lang_datefunc.html>
should be updated to, but that's just a single change 59 -> 60
B.T.W., try "man strftime" on Ubuntu:
> %S The second as a decimal number (range 00 to 60). (The range is
> up to 60 to allow for occasional leap seconds.)
It looks like the POSIX strftime() function is already
adapted to handle this 'problem' exactly the same way.
Regards,
Jan Nijtmans
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
