On Nov 20, 2018, at 12:41 PM, Jens Alfke <j...@mooseyard.com> wrote:
> On Nov 20, 2018, at 11:44 AM, Bill Hashman <bill.hash...@protocad-inc.com>
> wrote:
>
>> The timestamp from iOS systems is not compliant with ISO 8601/Unix or other
>> common timestamps. It appears apple has their start date offset 31 years.
>
> Yes, the ‘epoch’ in Apple’s own APIs (CoreFoundation, Foundation) is
> 1/1/2001, expressed as a double. But of course the POSIX APIs on Apple
> platforms use the regular Unix epoch of 1/1/1970 as integer.
That database looks like it was produced by Core Data, which does not use
SQLite's timestamp-specific features since NSDate and friends are backed by
doubles.
For Bill's purposes—investigating a copied, non-corrupt database—it would
probably be easiest to just convert from the Cocoa epoch to the Unix epoch by
updating all the columns that currently store Cocoa timestamps. Something like:
UPDATE ZTIMEENTRY SET ZDATE = ZDATE + 978307200;
Scott
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
