Re: Core Data : Opt Out of SQLite WAL is nullified after File > Duplicate ?
Re: Core Data : Opt Out of SQLite WAL is nullified after File > Duplicate ?
- Subject: Re: Core Data : Opt Out of SQLite WAL is nullified after File > Duplicate ?
- From: Feedback RhapSoft <email@hidden>
- Date: Tue, 28 Jan 2014 08:13:36 +0100
Hi Mike,
For your packaged store, I think wal is a better solution as Apple as chosen to enable it by default on both OSX and iOS. But for NSPersistentDocument, this is the wrong choice as documents must be made of one file to avoid confusion for users manipulating files manually in the finder (even if the rollback journaling mode with "delete" option could produce a temporary journaling file too).
About the Duplicate / Save As bug :
I have also raised an incident. The DTS person from Apple confirmed to me that this is a bug and agree with me that there are two workarounds :
- Temporary change the Base SDK back to 10.8 (very near term solution that I have chosen)
- Use method swizzling on NSPersistentStoreCoordinator method "- (NSPersistentStore *)migratePersistentStore:store toURL:URL options:options withType:storeType error:error" to pass the same store options as the original store. (swizzling is dangerous but I might use it when I need to use 10.9 Base SDK)
Romain.
Le 25 janv. 2014 à 23:23, Mike Abdullah <email@hidden> a écrit :
>
> On 21 Jan 2014, at 21:24, Jerry Krinock <email@hidden> wrote:
>
>>
>> On 2014 Jan 21, at 09:02, Mike Abdullah <email@hidden> wrote:
>>
>>> If it helps, I maintain https://github.com/karelia/BSManagedDocument as a nice way to have a package-based document using Core Data.
>>
>> Thank you, Mike. Now I have two reasons to start using BSManagedDocument :)
>>
>> Also, I have now confirmed the bug with a sample project and filed it, see below.
>
> Thanks Jerry.
>
> Sadly yes, some sort of migration would be required if you weren’t using a package-based format to start with (if you were, there’s a decent variety of hooks available in BSManagedDocument to customise it to match your existing layout).
>
> Presently BSManagedDocument is set up to configure Core Data to use the old-style journal (as I still support 10.6). However, the more I read on the subject, the more I wonder if this is worth it. Since the actual persistent store is kept safely hidden from the user inside of the package, is there actually any harm in using the new style journal, does anybody know?
>
>
> _______________________________________________
>
> 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
_______________________________________________
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