Now that the JPA 2.2 Review Ballot was approved, let’s start analyzing some of the new additions to the standard which have been supported by Hibernate for quite some time already. In this article, we are going to see how the JPA 2.2 Stream query results are supported by Hibernate and the caveats of using database cursors just to limit the amount of data that needs to be fetched.
Continue reading “What’s new in JPA 2.2 – Stream the result of a Query execution”
I read a very interesting article by Krešimir Nesek regarding MySQL result set streaming when it comes to reducing memory usage.
Mark Paluch, from Spring Data, asked if we could turn the MySQL result set streaming by default whenever we are using
That being said, the HHH-11260 issue was created, and I started working on it. During Peer Review, Steve Ebersole (Hibernate ORM team leader) and Sanne Grinovero (Hibernate Search Team Leader) expressed their concerns regarding making such a change.
First of all, the MySQL result set streaming has the following caveats:
ResultSet must be traversed fully before issuing any other SQL statement
- the statement is not closed if there are still records to be read in the associated
- the locks associated with the underlying SQL statement that is being streamed are released when the transaction is ended (either commit or rollback).
Continue reading “How does MySQL result set streaming perform vs fetching the whole JDBC ResultSet at once”