On Fri, Jun 27, 2014 at 9:11 AM, Jan Nijtmans <[email protected]> wrote:
> 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> > As a side-note: the /reports pages use Week #0 in some cases... because sqlite3 does it that way. > The general rule should be: be generous in what you accept, > strict in what you generate. With the caveat that if sqlite3 generates it, then it's automatically OK ;). > This means that fossil should never > generate an hour value of 24, but accepting it during > parsing should be no harm. +1 -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
