Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COThanks, I'll bear the comment about conventions in mind for the future - I'm new to Core Data. I still have a problem with the AND though: 2011-05-15 17:52:24.346 CL Places[14321:207] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'keypath isFavourite not found in entity <NSSQLEntity Location id=1>' I'm guessing that's because isFavourite is on the Photo object, not the Location. photosTookThere is an NSSet. How do I tell the predicate that this is an NSSet and that isFavourite should be checked on each member of the set?
      singulars
    2. COI see. Yeah the problem is that one argument is for locations and the other for photos. I think your naming of the relations mess me up. If I understand you correctly, then you will be fetching for photos, so your NSEntityDescription should be reflecting that. What you will want to do is have the location object on hand that you are querying for. You would then change the predicate to @"(whereTook == %@) AND (isFavourite == %@)", [self location], [NSNumber numberWithBool:YES]. With [self location] being replaced with wherever you have the location object. Hope this helps.
      singulars
    3. COThanks; still having a bit of bother but I'm going to do some additional background reading just in case I'm missing something really obvious. I might even rename the relations so they conform to the proper conventions whilst I'm at it.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload