It may or may not be a valid timestamp depending on what your time representation is. SQLite does not use UTC (which is an artificial timescale maintained by a bunch of atomic clocks). SQLite (and most other things that keep time, other than artificial atomic clocks) use Mean Solar Time.
The rules for Solar Time are that a day contains 24 hours, an hour contains 60 minutes, and a minute contains 60 seconds. Period. There are no exceptions. The "length" of a second is variable. Were this not the case then one would not be able to know that the time represented by 1735-03-21 12:00 corresponded to the time when the sun was directly overhead on spring equinox of the year 1735. While the UTC (artificial atomic timescale) permits a minute to contain 59, 60, or 61 seconds in order to allow UTC to approximate (be corrected to) GMT, UTC is not GMT and is not based on Solar Time. It is a discontiguous timescale for machines based on the fluctuation of energy states at the quantum level in specific radioactive isotopes. It is not based on the revolution of the earth around its axis or of the earth around the sun, as is Mean Solar Time. Because UTC is a discontiguous scale which "steps" occasionally to keep the "current" UTC time in sync with "real time" (as in Mean Solar Time), there is no way to convert between the two without having a massive table of the discontiguities. All time calculations for days, months, years, day of week, leap years, and on and on are based on Solar Time, which is based on the rotation of the earth, and not the vibration of electrons between energy states in radioactive isotopes. So a "year" represents one rotation of the earth around the sun, and a "day" represents one rotation of the earth around its axis (less precession error, which is why it is Mean Solar Time, and not Apparent Solar Time). >-----Original Message----- >From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- >boun...@sqlite.org] On Behalf Of jose isaias cabrera >Sent: Monday, 28 July, 2014 10:38 >To: General Discussion of SQLite Database >Subject: Re: [sqlite] ISO time leap second. > > >"Igor Tandetnik" wote... > >> On 7/28/2014 11:49 AM, Jan Nijtmans wrote: >>> 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. > >> julianday('2012-06-30T23:59:60'), and how should it compare with > >I claim that I am not an expert, but is this one a valid ISO time stamp? >If >so, then that ISO must be revised, as that time does not really exists >ever. >As the clock changes from the 59 second to the 60, a set of updates for >minutes, hours, days, month and year, should happen and that 60 then >becomes >0. (Thinking out-loud) > >josé > > >_______________________________________________ >sqlite-users mailing list >sqlite-users@sqlite.org >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
