What about One-To-Many relations?
Laurențiu Macovei

server side relations?

seems like a good idea, but some questions around limitations:

This approach means you end up doing extra queries client side to find related items. which is fine, but you need to be already subscribed to the related collections. eg notes.authors.comments

Is there a way to maybe add the required subscriptions just-in-time before doing the subsequent queries, and use the callback when the subscription is ready to execute the related query? sounds a bit callback soupy but could be made transparent.

Separately, returned from a meteor method is just JSON data so any server calls data coming back would lose any transformations that were applied server side. Perhaps that process could be wrapped in some way that transforms were auto applied to relate different collections that were all part of a single JSON blob returned?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.