Hello! On Tuesday 29 December 2009 04:21:07 Simon Slavin wrote: > I agree that this is often an acceptable alternative. But > > * it's hard to decipher if you're reading the data by eye
SQLite internal juliandays format is not human readable too. > * the system does not deal with leap seconds correctly It's not the problem becouse the format precision is 1 second. > * the system terminates in 2038 (if you use Unix's old 32-bit standard) > * one day you may need to read the data on a non-unix platform In cross-platform Tcl: tclsh8.5 [~]clock format 100000000000 Wed Nov 16 12:46:40 MSK 5138 > Nevertheless, if your data starts off as a Unix epoch, it can be fast and > convenient to just store it without having to do any conversion. As example, Cisco devices and some Unix daemons produce datetime in this format. Best regards, Alexey Pechnikov. http://pechnikov.tel/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
