2014-06-27 2:07 GMT+02:00 Andy Goth <[email protected]>:
> Fossil accepts dates with days beyond the end of the month, so long as
> the day is not 32 or greater. It also accepts times 24:00:00 through
> 24:59:59.
>
> For example, 2014-02-31T24:59:59 is valid. I imagine it means 31 days
> after the start of the day before February 2014 began, plus 24 hours
> plus 59 minutes plus 59 seconds. (Assuming 24:00:00 is considered to
> be the end of the day. I'm not sure how to tell.)
>
> This may be intentional, in which case carry on. I don't mind. I
> just wanted to be sure limiting time wasn't inadvertently overlooked.
Just my 2c. Since fossil depends on SQLite for its date
functions, I think this is intentional. See:
<http://www.sqlite.org/lang_datefunc.html>
The only thing I noticed when looking in this list is that in order
to be ISO 8601 compatible, seconds from 0-60 should be
allowed, not only 0-59. (maybe SQLite already accepts a
seconds value of 60, I didn't test that, I think it should....)
The reason for this is the possible leap second which
is sometimes inserted as an additional second on the
last day in june or december.
<http://en.wikipedia.org/wiki/Leap_second>
The general rule should be: be generous in what you accept,
strict in what you generate. This means that fossil should never
generate an hour value of 24, but accepting it during
parsing should be no harm.
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
