A user sent me a corrupt document file. It won’t open. Yes, it’s a Core Data SQLite file, and dumping it using sqlite3 on the command line doesn’t help either. It looks like some bits got smashed at one point…
ZMACSTER INTEGER, ZUSERDESCRIPTION VARC ???,???????… Anyhow, I was wondering if Versions Browser could come to the rescue by restoring a recent version, even if Time Machine is not available. Of course, the problem for the user is that if the document won’t open, you can’t get into Versions Browser. Has anyone ever dealt with this? Is it worth while trying to dig into /.DocumentRevisions-V100? Or should I try and mess with the metadata somehow, to try and fool my app into thinking that it’s opening the corrupt file when in fact it’s opening a new empty file? Jerry Krinock _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
