Re: mutableSetValueForKey:, addObject:, and selector not found
Re: mutableSetValueForKey:, addObject:, and selector not found
- Subject: Re: mutableSetValueForKey:, addObject:, and selector not found
- From: Niko Matsakis <email@hidden>
- Date: Thu, 2 Jun 2005 13:16:47 +0200
Assuming I understand the schema correctly, the relationships are
not set up correctly -- Language's vocabulary and Word's language
relationships are not defined as inverses of each other...
This is because if I do so, I get a similar error much earlier, when
I attempt to set the @"language" property of the Word to the language
object [before it is added to the set].
In reality, this is the same problem. The error that I get is the
same, so what is happening is that the word is being added to the
language's vocabulary and invoking the same "didChange" notification,
causing the same error. I was merely attempting to scrape away as
many layers of abstraction as I could to get closer to see which
actual function call was causing the problem.
So once it is fixed I will restore the Inverse property.
As an aside, it is confusing that the persistent document subclass
is given the same name as one of the entities.
Yes, I can see why that would be confusing. As it happens, that
entity is a singleton --- i.e., there is only one instance, and it is
created automatically along w/ the main document subclass, so there
is a one-to-one relationship, but I should change the name to
DictionaryDocument or something.
Niko
_______________________________________________
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