Re: Weird problem with Core Data
Re: Weird problem with Core Data
- Subject: Re: Weird problem with Core Data
- From: Ron Lue-Sang <email@hidden>
- Date: Fri, 20 Jan 2006 14:23:04 -0800
If you're not using an array/tree controller anywhere, then you might
look for any place that you call
[foo setValue:anArray forKey:@"toManyRelationshipKey"]
or
[foo setToManyRelationship:anArray]
In general you should mutate CoreData toMany relationships using
NSMutableSet *relationshipContent = [foo
mutableSetValueForKey:@"toManyRelationshipKey"]
and then mutate the resultant set.
From your earlier message, it sounds like newsItems is getting
replaced by an array. If you break at the start of addNewsItemsObject
and po [self valueForKey:@"newsItems"], what do you get?
-----------------------------
Ronzilla
Core Bindings/Cocoa Data
On Jan 20, 2006, at 1:32 PM, email@hidden wrote:
Message: 7
Date: Fri, 20 Jan 2006 22:01:39 +0100
From: Don Willems <email@hidden>
Subject: Re: Weird problem with Core Data
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Probably a bad binding. - member is a method for NSSet, but its being
called to NSArray
It sounds like you may have bound an NSArrayController's contentArray
to a to-many relationship of a Core Data entity, rather than the
NSArrayController's contentSet.
Actually I do not use bindings, I only use Core Data programatically.
So therefore it can't be a bad binding right?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden