On 2014 Jan 25, at 14:23, Mike Abdullah mabdul...@karelia.com wrote:
is there actually any harm in using the new style journal, does anybody know?
The bug reported by Glenn Austin in this thread, that future store migrations
may cause data loss for some users, seems pretty serious to me.
On 2014 Jan 26, at 20:28, Glenn L. Austin gl...@austin-soft.com wrote:
Migration may fail as the WAL file for the old store isn't removed before
attempting to open the new, migrated store -- which doesn't match the old
store's WAL file…
Glenn, just to be clear, is the “migration” you are
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
On Jan 25, 2014, at 2:23 PM, Mike Abdullah mabdul...@karelia.com wrote:
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
On 21 Jan 2014, at 21:24, Jerry Krinock je...@ieee.org wrote:
On 2014 Jan 21, at 09:02, Mike Abdullah mabdul...@karelia.com 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
On 2014 Jan 20, at 09:50, Sean McBride s...@rogue-research.com wrote:
I opt out of WAL in
configurePersistentStoreCoordinatorForURL:ofType:modelConfiguration:storeOptions:error:,
but my official buildbot is not actually linking against the 10.9 SDK yet,
so my experience may not count for
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:
I opt out of WAL in configurePersis
tentStoreCoordinatorForURL:ofType:mod
elConfiguration:storeOptions:error:, but my official buildbot is not
actually linking against
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
On 2014 Jan 21, at 09:02, Mike Abdullah mabdul...@karelia.com 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
On Sat, 18 Jan 2014 14:34:46 -0800, Jerry Krinock said:
In a post today in the Developer Forums [1], developer Romain Piveteau
mentioned in discussing another topic that, in a Core Data app, he “can
not disable journaling mode” (by which I presume he means that setting
the journaling mode to the
In a post today in the Developer Forums [1], developer Romain Piveteau
mentioned in discussing another topic that, in a Core Data app, he “can not
disable journaling mode” (by which I presume he means that setting the
journaling mode to the legacy “rollback” mode [2] is ineffective) when the
11 matches
Mail list logo
