Ah! He was relating objects in different contexts. I feel like CD could've given us a more informative error code here.
On Aug 5, 2010, at 14:24:05, Rick Mann wrote: > My co-worker is experiencing an odd problem in our Core Data app (iOS 3.2). > We have code that assigns one object to a property of another: > > Foo* foo = instance of DerivedFoo; > Baz* baz = instance of DerivedBaz; > > foo.myBaz = baz; > > In this case, foo and baz are both Core Data entities with explicit class > implementations defining the properties. myBaz is a CD relationship property > of type Baz*. The actual instances of both foo and baz are of derived classes > DerivedFoo and DerivedBaz. > > When the assignment happens, we get an exception complaining about coercion. > My co-worker isn't around, so I can't get the exact stack trace. I'm hoping > someone has seen this and knows what I'm talking about. I'll post more > details when he comes back. > > Any ideas? Thanks! > > -- > Rick > > _______________________________________________ > > 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: > http://lists.apple.com/mailman/options/cocoa-dev/rmann%40latencyzero.com > > This email sent to rm...@latencyzero.com _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
