-
Notifications
You must be signed in to change notification settings - Fork 3k
Add setting quarkus.hibernate-orm.query.fail-on-pagination-over-collection-fetch
#48265
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
Conversation
/cc @gsmet (hibernate-orm) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
🎊 PR Preview e19d60e has been successfully built and deployed to https://quarkus-pr-main-48265-preview.surge.sh/version/main/guides/
|
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well done.
...ent/src/main/java/io/quarkus/hibernate/orm/deployment/HibernateOrmConfigPersistenceUnit.java
Outdated
Show resolved
Hide resolved
This comment has been minimized.
This comment has been minimized.
I was told in https://hibernate.zulipchat.com/#narrow/channel/132094-hibernate-orm-dev/topic/hibernate.2Equery.2Efail_on_pagination_over_collection_fetch/with/522760198 that the performance issue can (and maybe is) mitigated with some automatic override of the JDBC fetch size. |
quarkus.hibernate-orm.query.fail-on-pagination-over-collection-fetch
and have it default to true
quarkus.hibernate-orm.query.fail-on-pagination-over-collection-fetch
Status for workflow
|
Status for workflow
|
Fixes #36922
No breaking change, no migration guide entry.