On 25 Aug 2017, at 1:19am, Jens Alfke <j...@mooseyard.com> wrote:
> The only drawbacks of numeric timestamps are that > (a) they don't directly store a timezone (you have to add that as another > column), and > (b) they don't make it easy to do calendar operations like getting the month > or year (but for I18N purposes you don't want to hardcode Western calendars > into your code anyway.) Either part of (b) or item (c): Numeric timestamps make it easy to do "24 hours after this timestamp". But they make it difficult to do "9am the next day". Because of this, in cases where filespace is not a problem I’ve sometimes stored both Unix epoch and a text timestamp. Yes, it’s redundant data, but I know that whatever calculation I need to do with the timestamp will be easy, and that speeds up both my program and my programming. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
