2014-07-28 17:10 GMT+02:00 Igor Tandetnik <i...@tandetnik.org>:
> All your fix does is have the parser accept "60" as valid seconds field.
> That's not very interesting.
Yes, that's exactly all that I'm after. ISO 8601 does not specify how
leap seconds are handled, it just specified which date-stamps are
valid and which not. It's perfectly OK for fossil/SQLite to ignore
the leap second, it's not OK that an error-message is produced
for a valid ISO 8601 time-stamp. ISO specifies that seconds
must be between 0 and 60, not between 0 and 59, just as hours
can be between 0 and 24, not between 0 and 23 (which
SQLite's parser adheres to)
<http://en.wikipedia.org/wiki/ISO_8601>
> ISO 8601 uses the 24-hour clock system. The basic format is [hh][mm][ss]
> and the extended format is [hh]:[mm]:[ss].
>
> [hh] refers to a zero-padded hour between 00 and 24 (where 24 is only used
> to denote midnight at the end of a calendar day).
> [mm] refers to a zero-padded minute between 00 and 59.
> [ss] refers to a zero-padded second between 00 and 60 (where 60 is only
> used to denote an added leap second).
That's not what SQLite implements (although it is very close....)
Regards,
Jan Nijtmans
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
