On Nov 26, 2018, at 14:16, Simon Slavin <slav...@bigfraud.org> wrote: > > On 26 Nov 2018, at 9:09pm, Scott Perry <num...@apple.com> wrote: > >> 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; > > If you want to access your date in that form but leave the database usable by > Apple's libraries you can create a view which has a new column which modifies > the date in the above way. As long as your VIEW's name does not clash with > one Apple wants to use, Apple's utilities should not stop working just > because you created a new view in a Core Data database. I have previously > done this without problems but I may have just been lucky. > > Come to think of that, Scott, you're in a better position to confirm that > than I am.
Local experimentation is one of the greatest learning tools, but I don't recommend making any customizations to Core Data stores that will ever be used on someone else's device as the framework is not especially sympathetic to meddling. With that disclaimer out of the way, as a general rule Core Data namespaces all of its resources by prefixing them with Z. Migrations (which occur when updating the store to a new model version, or on first use after an operating system update) may destroy schema customizations. Scott _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
