Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS Documentation Missing
- Thread starter teguh123
- Start date
- Sort by reaction score
if you still have trouble finding what you're looking for, go to developer.apple.com
That's your best bet for reference material pertaining to Xcode. Good luck.
That's your best bet for reference material pertaining to Xcode. Good luck.
Last edited by a moderator:
One Way Relationship in Core Data
Every restaurant must have Latitude and Longitude. However, every LatitudeLongitude object must not have "a restaurant"
So I have a one way relationship and generate a compiler warning.
What's the catch?
Should I use fetchRelationship instead? But what the hell is fetchRelationship?
Why is it one way? Why does it have predicate? Why it is called fetch? I read the documentation and doesn't seem to get what it really is.
Every restaurant must have Latitude and Longitude. However, every LatitudeLongitude object must not have "a restaurant"
So I have a one way relationship and generate a compiler warning.
What's the catch?
Should I use fetchRelationship instead? But what the hell is fetchRelationship?
Why is it one way? Why does it have predicate? Why it is called fetch? I read the documentation and doesn't seem to get what it really is.
You're using Core Data, right?
If you have a read about it it will say that Core Data really wants you to have a reverse relationship.
So if your Restaurant has a Location object (1-1) Then your Location Object need a Restaurant object (1-1) to point back to.
Core data uses this to ensure it won't end up with orphans.
If you have a read about it it will say that Core Data really wants you to have a reverse relationship.
So if your Restaurant has a Location object (1-1) Then your Location Object need a Restaurant object (1-1) to point back to.
Core data uses this to ensure it won't end up with orphans.