-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to do nested joins? #6
Comments
TLDR: No. Hey! No worries asking questions. It's extremely gratifying to have my work considered as a possible solution to your problem. I haven't worked on this since the last commit so it takes me a moment to recollect the exact state of the project. If you take a look at this version of the readme, particularly line 58: d0618c0#diff-04c6e90faac2675aa89e2176d2eec7d8R58 you will find a more complete example of usage and an exact answer to your question. Months ago I planned on adding this functionality but never got the opportunity to do so. I would accept a pull request adding it. |
Thank you! I will look through the code and see if I can work it out. When I got rid of the ORM I underestimated the difficulty of impedance-mismatch. Not only this, but after going through all my data models I realised that the majority of them can be denormalised entirely without having data duplication issues. Most of what I do doesn't require joins, except things like the example above. I have taken the plunge into MongoDB. |
I created a pull request. I hope I understood the join process correctly. Tell me what you think. |
I have another question (sorry!) that has to do with joins on nested data. Consider an example where I can have events, and each event can have a number of members:
The
participants.id
attribute is meant to be a reference to theid
attribute in theusers
document store, below:Is it possible to do a join such that I produce the following, below? Is it advisable?
Thank you for your time.
The text was updated successfully, but these errors were encountered: