Date parsing performance on iOS (NSDateformatter vs sqlite)

Post by MishraAnurag » Sun, Sep 08, 2013, 3:41 AM UTC

asveikau wrote: post #40

For those million timestamps I am sure that those extra allocations from the statement APIs are not helpful. Since he references the C code sqlite is using (at a quick glance it looks pretty contained) I don't know why he doesn't just include it directly in his project and call it from objc, no statement API needed. [Edit: I see now that in the test there is only 1 statement object ever created for a test of a millio…

Post by colanderman » Mon, Sep 09, 2013, 4:03 PM UTC

DannyBee wrote: post #56

colanderman wrote: post #17

Earlier quoted context omitted.

More importantly (the GP missed this as well), Unix timestamps can't convey local time . Local time has UI implications, e.g. the query "is this event on a weekend" is not generally answerable without the time zone.

Entirely true, but not necessarily relevant. Local time is a weird thing and changes all the time. For giggles, look at the history of timezone rule changes in tzdata. Most timezones have at least one duplicate hour per year (IE the same time occurs twice) in the US as well. Local times are not an appropriate way to store time. Note: ISO8601 does not give you local time anyway, since you cannot infer the timezone fro…