On 21 Jan 2014, at 16:11, Sean McBride <s...@rogue-research.com> wrote:

> On Tue, 21 Jan 2014 07:06:16 -0800, Jerry Krinock said:
> 
>> On 2014 Jan 20, at 09:50, Sean McBride <s...@rogue-research.com> wrote:
>> 
>> The trouble occurs if a developer of an older Core Data app begins to
>> link against the 10.9 SDK, and allows the *new* default journal_mode =
>> write-ahead logging to be used, but does not migrate the app’s document
>> to use the new “file package” format.  As far as the user is concerned,
>> the document file is still the sqlite database file.  The user may think
>> that the -shm and -wal files, which are occasionally produced by sqlite,
>> and appear along side the document file, are junk.  If such a user moves
>> the document file without moving the -shm or -wal file, or trashes the -
>> shm or -wal file, data corruption can occur.
> 
> Oh!  Is that the case?  The release notes don't mention anything like that.  
> So basically they expect/require you to use file packages?  And yet 
> NSPersistentDocument doesn't even support file packages!  It's right there in 
> the docs:
> 
> "Important: NSPersistentDocument does not support some document behaviors:
> File wrappers.
> See File Wrappers with Core Data Documents for an example of how you can add 
> support for file wrappers."
> 
> Then you go to that sample code and it says:
> 
> "Retired Document.  This sample code may not represent best practices for 
> current development"
> 
> What should we be concluding here? :(

If it helps, I maintain https://github.com/karelia/BSManagedDocument as a nice 
way to have a package-based document using Core Data.
_______________________________________________

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

Reply via email to