[17:25:47] <wereHamster> an index is an index, no matter what it indexes
[17:27:04] <timeturner> so embedding objectids of comments in a post and querying for the objectids of the comments and populating the post has the same performance hit as saving the post's objectid in each comment and querying for comments that hold that post's objectid and then sorting and embedding them into each post on the client side?
[17:28:02] <timeturner> only difference being that the array of objectids cannot go on forever I presume
[17:29:43] <wereHamster> well, yes. The only difference there is who is the parent in the parent-child relation (if you think in sql terms)
[17:30:42] <timeturner> well the parent is the post but the only difference is that the parent references the children vs the children referencing the parent
[17:32:01] <timeturner> the optionn where the parent references the children is appealing because then I can have mongoose populate and sort the children and insert them into the parent's field for me
[17:32:10] <timeturner> vs me having to carry that out manually