Relationships in Parse: It's Not Complicated - Parse Developer Day 2013
Why Stack Overflow recommends it
Stack Overflow users link it when answering Parse data modeling questions, such as choosing between pointers, arrays and relations, or how a child object should reference its parent.
Recommended by 3 people across 3 different months, 2014 to 2015.
What it is
A 2013 Parse Developer Day talk from Meta Developers on modeling relationships between objects in Parse. It walks through the common relationship scenarios, shows how to implement each with Parse, and discusses the tradeoffs between approaches.
What people said
Recommends knshn · 2014-10 · Stack Overflow · on “Should I use an array of pointers or a PFRelation? (parse.com)”
The question is about how you access your data. For your case, you can think about these questions: Do you need to include a user's TennisGames whenever you get a user? If yes, arrays support include on queries. You can't do include with relations and you need to do one more query to access a user's TennisGames. How many TennisGames will a user have at max? If it is likely to be more than 100 (recommended limit by Parse), it is better you go with relations. Because arrays don't scale to large relationships. As you pointed it out, is the order important for you? If yes, arrays support order. And again as you said, if you are interested a subset of data, relations are able to restrict queries
Recommends André Kuhlmann · 2015-04 · Stack Overflow · on “Ideas to store an TableView for different Users on Parse”
I have finally got it, thanks @unverschaemt he has helped me a lot :D Also I have found a great video on youtube -> link [this video]
Recommends Elkhan Mamedov · 2015-11 · Stack Overflow · on “Pointer to blog posts does not contain the replies that belong to the post (Parse, Swift, iOS)”
You may want to watch this [this video] Parse video. Reply belongs to a Post while Post doesn't have to belong to a reply. Plus, theres a whole bunch of information about the subject available
Cites cakl · 2015-07 · Stack Overflow · on “PFQuery returning objects where object's relation matches all conditions”
I'd use the array of pointers, because I assume there is a maximum number of tokens that can be set on one article. (AFAIK the limit is 1k Parse Docs [LINK] ) Parse says it makes sense if you know the max number (e.g postal codes). See Relationships in parse [this video] If an array of pointers is not a possible solution for you, I'd solve the n:m relation with your own class (e.g. HasToken or TokenRelationship) instead of PFRelation (or Array of pointers). @interface TokenRelationship : PFObject <PFSubclassing> @property (nonatomic, strong) Article article; @property (nonatomic, strong) SearchToken searchToken; @end Then perform a query on TokenRelationship with a subquery using whereKey:matches