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
For Hibernate Reactive enableCollectionInDefaultFetchGroup must be set to true #15814
Labels
Milestone
Comments
/cc @Sanne, @gavinking |
I already have a fix |
DavideD
added a commit
to DavideD/quarkus
that referenced
this issue
Mar 17, 2021
The default for ORM is false, but when we create the SessionFactory for Hibernate Reactive this value has to be true. For more details, see: hibernate/hibernate-reactive#663
DavideD
added a commit
to DavideD/quarkus
that referenced
this issue
Mar 17, 2021
DavideD
added a commit
to DavideD/quarkus
that referenced
this issue
Mar 17, 2021
DavideD
added a commit
to DavideD/quarkus
that referenced
this issue
Mar 17, 2021
DavideD
added a commit
to DavideD/quarkus
that referenced
this issue
Mar 17, 2021
DavideD
added a commit
to DavideD/quarkus
that referenced
this issue
Mar 17, 2021
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Mar 23, 2021
The default for ORM is false, but when we create the SessionFactory for Hibernate Reactive this value has to be true. For more details, see: hibernate/hibernate-reactive#663 (cherry picked from commit 76072c5)
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Mar 23, 2021
(cherry picked from commit bf9e86d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the Hibernate Reactive extension doesn't set the property and so
enableCollectionInDefaultFetchGroup
is set to false. This is the default value for ORM.The result is that when we try to fetch lazy collection we have a
LazyInitializationException
errors.See this issue on Hibernate Reactive for more details: hibernate/hibernate-reactive#663
Example of code causing the exception:
The text was updated successfully, but these errors were encountered: