When using NSPersistentDocument it takes over responsibility for saving the context. You should not save the context yourself.
> On 18 Oct 2014, at 17:00, Luther Baker <lutherba...@gmail.com> wrote: > > Hi, > > I am creating a Desktop issue tracking app using core data and the > NSDocument framework - so yes, the Xcode wizard extended > NSPersistentDocument which provides me with an NSManagedObjectContext. > > My question is - if I start working in the app, creating issues for > instance ... when I go to actually persist the context I get an error "This > NSPersistentStoreCoordinator has no persistent stores. It cannot perform a > save operation." > > So, does this imply that for NSDocument style programming, most folks > aren't 'saving' their context right away? Do we wait for the user to > actually save the document the first time? IE: there is not in memory store > that the Document manages until the user formally saves to the file system? > > And does it follow then that on subsequent changes, we formally persist the > context only when the user actually 'Saves'? > > Does anyone force the user to 'find' a file location right away, upon > opening a new document, and then persist everything happily in the > background? > > I tend to this this is really just a Desktop paradigm question more than > anything else. _______________________________________________ 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
