Skip to content
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

Extend ORM to handle Joins #56

lewsid opened this issue Mar 19, 2020 · 0 comments

Extend ORM to handle Joins #56

lewsid opened this issue Mar 19, 2020 · 0 comments


Copy link

@lewsid lewsid commented Mar 19, 2020


I guess what I find lacking is that the ORM support doesn’t an easy way to query against related tables. I get not wanting to hydrate all the joined data, but being able to stick a related field in the where clause (and then the ORM would implicitly add a join to the query) and then only returning/hydrating one model would save me from having to write 75% of the raw queries I end up writing.

Or even just getWith, but with a table_name.field_name convention. The schema would have to be aware of these relationships to make something like that happen, though. I don’t think it would be a huge lift, and I can imagine ways that it could be layered on top of what we have know without breaking anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.