--Original Message-
> From: cocoa-dev-bounces+jmunson=his@lists.apple.com [mailto:cocoa-dev-
> bounces+jmunson=his@lists.apple.com] On Behalf Of I. Savant
> Sent: Monday, April 27, 2009 4:54 PM
> To: Walker Argendeli
> Cc: cocoa-dev@lists.apple.com
> Subject: Re: Core Data
On Mon, Apr 27, 2009 at 4:50 PM, Walker Argendeli
wrote:
> All I've done is bind controls in IB to values in Core Data. (I'm not very
> experienced with it yet)
Learn to use the debugger. Set a breakpoint on your save routine and
step through the code, examining the results.
We can't do any
All I've done is bind controls in IB to values in Core Data. (I'm not
very experienced with it yet)
Core-Data-Wise, I have a data model and an AppDelegate file where I
specified addPersistenStoreWithType: etc.
The persistent store is now empty when I look at it, although I know
it's had data
Is your call to save: the managed object context succeeding?
... what does that managed object context return for hasChanges?
... and are the objects you expect to be saved in the
insertedObjects, updatedObjects, deletedObjects collections?
... is save returning an error?
And
Thanks for the suggestion. I tried it, but no go.
It's core data based, but not document-based
I've just got the application loading all its data from core data
I'm running 10.5.6 with Xcode 3.1.2
I'm relatively new to Core Data, but I've been developing this
application for a few months now an
On 2009 Apr 26, at 16:23, Walker Argendeli wrote:
I've been working on a project that uses Core Data for a while now.
I recently changed the model and ran it, but I noticed an odd
behavior: I wan't informed that the model had changed and was
incompatible. I went ahead and deleted the old
I've been working on a project that uses Core Data for a while now. I
recently changed the model and ran it, but I noticed an odd behavior:
I wan't informed that the model had changed and was incompatible. I
went ahead and deleted the old xml file and when running the
application again, i
