I'm not using autosave. In fact this is done in my document controller before
the NSPersistentDocument is even created. Does the Core Data stack have some
awareness of an autosave mode? Perhaps, as you suggest, Apple has dropped this
feature and this is just a documentation bug. Hope someone fro
On 2011 Jul 31, at 21:18, Dave Fernandes wrote:
> I just found a strange thing on Lion: the backup~ file doesn't get produced
> with in-place lightweight migration. The same binary *does* create the
> backup~ file on Snow Leopard, though. Has anyone else noticed this?
Have not noticed it becau
I just found a strange thing on Lion: the backup~ file doesn't get produced
with in-place lightweight migration. The same binary *does* create the backup~
file on Snow Leopard, though. Has anyone else noticed this?
On 2011-07-21, at 8:31 AM, Roland King wrote:
> I suppose I had to get to core
On 2011-07-21, at 12:16 PM, Roland King wrote:
> Great - thanks for this - gets me started, I've found the documentation quite
> dense and soon I have to pitch in and just give it a go (I have a model I
> need to update in my test app and I really don't want to toss the data).
>
> I need to h
Great - thanks for this - gets me started, I've found the documentation quite
dense and soon I have to pitch in and just give it a go (I have a model I need
to update in my test app and I really don't want to toss the data).
I need to hunt around the NSManagedObjectModel class a bit more, clear
Yes, if you want the file deleted you have to do it yourself. There are
certainly cases where you would not want to delete the file. For example for a
document, the user may want to keep that archive around in case they need to
revert to a previous version of the app, or share it with someone el
