Re: CoreData warning: File.children -- to-many relationship does not have an inverse:
Re: CoreData warning: File.children -- to-many relationship does not have an inverse:
- Subject: Re: CoreData warning: File.children -- to-many relationship does not have an inverse:
- From: Quincey Morris <email@hidden>
- Date: Wed, 4 Aug 2010 15:03:08 -0700
On Aug 4, 2010, at 10:50, Ignacio Enriquez wrote:
> "Child" entity relationships:
> Child.children ->> Child and its inverse : parentChild #1
> Child.parentChild ->>Child and its inverse : children #2
> Child.parentFile ->> File and its inverse: children #3
>
> "File" entity relationships:
> File.children->>Child and its inverse: parentChild #4
> File.files->>File and its inverse: parentFile #5
> File.parentFile->>File and its inverse: files #6
>
> I understood why #1, #2, #5 and #6 are the way they are but why is #3 and #4?
There's something wrong here. #4 is the inverse of #3, so it should say "and its inverse: parentFile", shouldn't it. Otherwise it would conflict with #1 and give you a warning. So I'm guessing this is just a typo in your post?
One way you clarify all of this would be to rename all your relationships in a clearer way. (And, possibly, to rename the Child entity, since "Child" sort of conflicts with the loose parent/"child" relationship terminology that we could use for both hierarchies.)
So, you could say that Child's 3 relationships are childSubnodesOfChild, parentChildOfChild and parentFileOfChild. The File's 3 relationships are fileSubnodesOfFile, childSubnodesOfFile and parentFileOfFile. Does that make it any clearer?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden