On 29 Jul 2014, at 5:36am, Nico Williams <n...@cryptonector.com> wrote:
> Note that SQLite3 apparently does no > corrections for leap seconds anyways in date arithmetic (which it > can't do if you're using numeric arithmetic on Julian days anyways!), > which it would have to do (since UTC is non-uniform). I'm not > entirely sure what it means for anyone who really cares about TAI, or > who they might be besides astronomers. If all you want to do is parse > dates, then indeed, raising an error would be better than ignoring a > leap second, but if you want to do any arithmetic on dates, then > you're already in trouble, given which I think the fair thing to do is > ignore leap seconds, but I'll freely admit that it's not ideal. Agree with all of that. You're never going to get non-scientific programmers to do this properly anyway. Every financial programmer knows that there are exactly 60*60*24 = 86,400 seconds in a day. You've never going to get them to use library routines to work out how many seconds there are in a 30 day period. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
