fetchRelated() confusion about backbone-relational HOT 2 CLOSED

Yes, it should; but it does determine which objects to fetch based on the id's that you currently have specified in the relation. For an example, you could take a look at the tests for HasOne and HasMany.

from backbone-relational.

Ah, I think I understand the purpose of this function now. It's for fetching known related records that you just haven't loaded into Backbone yet. I kinda figured I would use it to fetch only newly added records for a set, but you need to know the ids of those records first.... so fetch really is what I needed.

That does beg the question of loading records from the database that you don't have on the client side, though... so you could send all of the ids for the Backbonified records to the server, make a routine to send back the missing relations, and turn them into Backbone objects when you get the response... Hmm.

For example, I have a Post with comments 1, 2 and 3, but comments 4 and 5 happen after I've loaded my initial Backbone object... when I navigate to see the comments, it could perform the routine above--sending the server comment ids 1, 2, and 3, and bring back only comments 4 and 5 to add to my collection.

Seems useful, but maybe overkill when a normal fetch() might be just as fast?... unless we're talking about hundreds of comments or something.

from backbone-relational.