Persisting Dates to SQLite3 in an iPhone Application
I typically use a double, something like:
sqlite3_bind_double(statement, index, [dateObject timeIntervalSince1970]);where dateObject is an NSDate*. Then, when getting the data out of the DB, use
[NSDate dateWithTimeIntervalSince1970:doubleValueFromDatabase];
Store as a typical C-time (e.g. the time_t/int value returned by time()) value in an UNSIGNED INT column. Convert like drewh said with NSDate:
- timeIntervalSince1970- dateWithTimeIntervalSince1970:(double)valueExcept store as an integer, unless you need sub-second granularity (which, generally, for created-on/last-modified, is overkill). Unsigned ints are a lot smaller and easier to process than doubles. While this may not matter in most desktop and web applications anymore, it certainly helps on the iPhone. Every little bit helps.
One side benefit of C-times that most people don't realize is that they're timezone-agnostic. If you ever need to support multiple timezones, this comes in handy.
I convert to/from ISO8601 strings: http://en.wikipedia.org/wiki/ISO_8601
Far more readible/hackable than time intervals.