-
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
Performance compared to Mongoose #8
Comments
I don't know offhand what the performance difference is. Also sorry about
|
I notice as well that there is no way to select the columns wanted from the joining collection. I can create a new pull request for this. |
Yeah that's a good idea. A lot of web frameworks support field filtering.
|
Yeah it would be especially useful if you are joining on a user's table, which is probably the most common use case for this. |
At first glance it looks like I just need to add a projection operator to the |
Not sure. I'm on my phone right now, but yes a projection will work. As
|
I made a minor addition to my initial pull request (small error where
leftKeys.split('.')
should have beenleftKeys[0].split('.')
) and it works perfectly on my system in doing nested joins.My question is: do you know the performance of this compared to the ad-hoc joins performed in
Mongoose
? I never cared much for ORMs or ODMs, but I was just curious.The text was updated successfully, but these errors were encountered: