The GNSS systems do of course know when leap seconds occur, one of their purposes is to communicate accurately UTC. But unlike system clocks of computers which often are halted during leap seconds or slowed down before them, to avoid complications, the satellites will transmit their codes strictly also over leap seconds, and orbital information like elevation is available in these. Therefore my advice to use on the Sqlite level a day segmented two column time stamp in this particular case. It is also handy if queries are for certain dates or date intervals, perhaps the performance for such queries even increases compared to a single column time unit counter?
The GNSS systems use internally their own time, one of them is GPS time. To the consumer normally UTC is provided, which I assume is also here the case. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
