-
Notifications
You must be signed in to change notification settings - Fork 173
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
Problem with join fetch in library #58
Milestone
Comments
ThienPhuc92
changed the title
Search with multi column
Problem with join fetch in library
Jul 4, 2017
Hi, sorry for the delay! It seems you're absolutely right, that's something we should fix. Could you provide the code of the |
darrachequesne
added a commit
that referenced
this issue
Dec 4, 2017
Previously, a @onetomany relationship could trigger multiple join fetch. Now, there is a maximum of two 'LEFT JOIN' clauses, one for filtering and one for fetching. This was made possible by converting the input to a tree. Example: - name - company.id - company.name - company.description - company.ceo.name - company.ceo.age Tree: - name - company --- name --- description --- ceo ----- name ----- age Closes #58
darrachequesne
added a commit
that referenced
this issue
Dec 5, 2017
Previously, a @onetomany relationship could trigger multiple join fetch. Now, there is a maximum of two 'LEFT JOIN' clauses, one for filtering and one for fetching. This was made possible by converting the input to a tree. Example: - name - company.id - company.name - company.description - company.ceo.name - company.ceo.age Tree: - name - company --- name --- description --- ceo ----- name ----- age Closes #58
darrachequesne
added a commit
that referenced
this issue
Dec 10, 2017
Previously, a @onetomany relationship could trigger multiple join fetch. Now, there is a maximum of two 'LEFT JOIN' clauses, one for filtering and one for fetching. This was made possible by converting the input to a tree. Example: - name - company.id - company.name - company.description - company.ceo.name - company.ceo.age Tree: - name - company --- name --- description --- ceo ----- name ----- age Closes #58
darrachequesne
added a commit
that referenced
this issue
Dec 10, 2017
Previously, a @onetomany relationship could trigger multiple join fetch. Now, there is a maximum of two 'LEFT JOIN' clauses, one for filtering and one for fetching. This was made possible by converting the input to a tree. Example: - name - company.id - company.name - company.description - company.ceo.name - company.ceo.age Tree: - name - company --- name --- description --- ceo ----- name ----- age Closes #58
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Darrachequese,
The first, my english is not very well, so maybe some thing i explain about your problem will make you confusing. I'm sorry about that.
I had use your library, but i think your library has some problem.
Your code:
Example:
You join fetch 2 table: A, B, then you want to find all result with predicate p1, and predicate p2 on table B.
your query will be -> SELECT * FROM A a1 JOIN FETCH a1.b b1 JOIN FETCH a1.b b2 WHERE (b1 has p1) AND (b2 has p2).
Right query: SELECT * FROM A a1 JOIN FETCH a1.b b1 WHERE (b1 has p1) AND (b1 has p2)
I resolved this by i convert all column into a tree. A tree will ensure no column duplicate. So i can make right query. But my code is not clean. I wish you improve your library. Some of my code. Hope you consider it to me
Edit: code style
The text was updated successfully, but these errors were encountered: