-
Notifications
You must be signed in to change notification settings - Fork 465
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
Limit Query in Post resolver : limit instead of take #29
Comments
You, my friend, are a lifesaver. I was hesitant on trying Ben's solution on using raw SQL for joining and then mapping the values using json function, but since this works it has saved me hours. Many thanks. |
I think there is still a bit more optimization that could be done here. For example, this will always join the post and user table, even if the query didn't ask for the |
Thank you! This is great, I thought having to write SQL was a bit more effort and assumed it could have been achieved with the Although, I think;
should be
and in the return
Or instead of For the |
Possible solution typeorm/typeorm#747 (comment) |
Thank you so much for this course @benawad, I am almost into 8 hours in it and i started with MongoDB and it worked well until Query Builder started :) so switch to Postgres
Found that we can still query using queryBuilder
also the query looks much more cleaner than using "take"
Found this here
The text was updated successfully, but these errors were encountered: