Re: Checking integrity of a Core Data document with SQLite store
Re: Checking integrity of a Core Data document with SQLite store
- Subject: Re: Checking integrity of a Core Data document with SQLite store
- From: Dave Fernandes <email@hidden>
- Date: Mon, 15 Mar 2010 22:49:49 -0400
On 2010-03-15, at 3:30 PM, Ben Trumbull wrote:
> Running an integrity check can be useful if you have previously gotten a corrupt db error back from fetching or saving, or your app previously crashed, or you have some other active indicator it might be worthwhile. However, it's quiet expensive in I/O and you should not do it on every app launch / document open. Customers with account home directories on AFP, NFS or SMB servers will be very unhappy, and if your files become large enough so will people using local drives.
That's a shame. It would certainly be easier to check when opening the file than to scatter code all over the app to diagnose the problem. Is there a standard exception I can expect to get when fetching or saving? NSInternalInconsistencyException is the one I currently get.
Thanks,
Dave_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden