SQLite Forum

Proposed slightly-incompatible change to date-time functions
I know I am currently working on one that does, and I find it hard to imagine that others would not.

The key is that Julian date (or minor modifications on it) are a very good compact method to store historical dates.

If you are only concerned about DATE, and not the time, then the Julian Day Number as an integer is an ideal storage format, no need to waste 8 bytes when less will do.

And if dealing with historical times Julian Dates as floats have problems that there represent the time in GMT, not local, and it is unlikely that you have the time specified as GMT, and if you want to actually DO anything with those values you need to know your local time offset (not just 'time zone, as those didn't exist yet).