It seems that I failed to make the point clear:
On June 30, 2012 the 86401st second happened in the real world, it was working time in parts of the US. In this second there were financial transactions, photos were taken, sensors delivered data, etc etc, events that users might want to insert into databases with a correct time stamp, and where the seconds might matter. This is of course possible, for example, by using a string like '2012-06-30T23:59:60', or by using separate columns for year, month, day, hour, min, sec, or by constructing a custom numeric time stamp counting the really elapsed seconds and fractions of seconds from some epoch, an example is the astronomical Julian Day. However, Sqlite's julianday seems to have limitations because it returns NULL for times that fall in leap seconds (in addition, it is off by presently about 1 min from the Julian Day that is used in astronomy). Perhaps the reason is that leap second times cannot be represented with a syntactically valid time string, per http://www.sqlite.org/lang_datefunc.html, but it really doesn't matter much what the reason is. I'm suggesting, that Sqlite should have a function that for the convenience of users returns a monotonically increasing numeric timestamp for all practical times in the real world, including the leap seconds. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
