-
Notifications
You must be signed in to change notification settings - Fork 95
Upgrade to Hibernate ORM 7.0.0.Beta5 #2155
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
Milestone
Comments
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Mar 25, 2025
Some of the changes: * NullabilityCheck has changed * Remove ReactiveQueryImplementor#setOptional* * Replace inline calls to BatchFetchQueueHelper (removed)
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Mar 25, 2025
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Mar 25, 2025
Some of the changes: * NullabilityCheck has changed * Remove ReactiveQueryImplementor#setOptional* * Replace inline calls to BatchFetchQueueHelper (removed)
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Mar 25, 2025
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Mar 25, 2025
Some of the changes: * NullabilityCheck has changed * Remove ReactiveQueryImplementor#setOptional* * Replace inline calls to BatchFetchQueueHelper (removed)
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Mar 25, 2025
DavideD
added a commit
that referenced
this issue
Mar 26, 2025
Some of the changes: * NullabilityCheck has changed * Remove ReactiveQueryImplementor#setOptional* * Replace inline calls to BatchFetchQueueHelper (removed)
DavideD
added a commit
that referenced
this issue
Mar 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would seem the latest version of Hibernate Reactive 3 is not compatible. Getting things like this in my Quarkus upgrade PR (quarkusio/quarkus#41310):
The text was updated successfully, but these errors were encountered: