On 5/22/2013 5:28 PM, Stephan Buchert wrote:
Sqlite's julianday in the leap second seems to be NULL:sqlite> select julianday('2012-06-30T23:59:60')*86400;
So is julianday('foobar'). '2012-06-30T23:59:60' is simply not a syntactically valid time string, per http://www.sqlite.org/lang_datefunc.html
For comparison, the mktime function of the standard library in my computer (CET) returns 1341093599, 1341093600, 1341093600 for the times 2012-06-30T23:59:59, 2012-06-30T23:59:60, and 2012-07-31T00:00:00, respectively.
mktime also accepts 2012-06-30T23:59:61, 2012-06-30T23:59:62 and so on, as well as, say, 2012-15-35T00:00:00. This has nothing to do with leap seconds, and everything to do with the fact that mktime accepts values out of range and automatically normalizes them.
-- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
