@vladmihalcea Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@vladmihalcea Thank you for signing the Contributor License Agreement!

As per our JIRA discussion, this has been rolled into master in a slightly extended fashion, only applying setDefaultReadOnly(true) to transaction-local resources... which means no side effects for later access, and no cleanup neessary. Thanks for the PR, in any case!

@jhoeller was similar behaviour ever implemented for Hibernate 6?

@jwgmeligmeyling Yes, the optimizations work just fine with Hibernate 6 because they are applied by the HibernateJpaDialect.

Check out this line in the HibernateJpaDialect for more details.