Optimistic locking version property with JPA and Hibernate
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
Introduction
In this article, we are going to see how optimistic locking version property works when using JPA and Hibernate.
Most often, we overlook basic concepts and focus only on more advanced topics such as associations or queries, without realizing that basic mappings can also have a significant impact when it comes to persistence effectiveness and efficiency.
Optimistic locking version property with JPA and Hibernate@vlad_mihalcea https://t.co/mcESSRxB48 pic.twitter.com/oOHIgkhZDl
— Java (@java) June 13, 2019
Tuning Spring Petclinic JPA and Hibernate configuration with Hypersistence Optimizer
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
Introduction
In this article, we are going to see how we can tune the performance of the Spring Petclinic application using Hypersistence Optimizer.
Now, while you can manually analyze your data access layer to make sure that JPA and Hibernate are properly configured, it’s much better if you can automate this task. That’s because new entities might be mapped in the future, and you want to make sure that the same performance-specific rules are consistently applied on every commit.
Hypersistence Optimizer allows you to automatically detect JPA and Hibernate issues during development, so you can optimize your application long before you launch it into production.
How to intercept and modify SQL queries with the Hibernate StatementInspector
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
Introduction
A very useful, yet lesser-known, Hibernate feature is the ability to intercept and modify any auto-generated SQL statement using the Hibernate StatementInspector utility.
In this article, we are going to see how the Hibernate StatementInspector mechanism works.
How to detect HHH000104 issues with hibernate.query.fail_on_pagination_over_collection_fetch
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
Introduction
Recently, I noticed the hibernate.query.fail_on_pagination_over_collection_fetch configuration property that was introduced in Hibernate 5.2, and I had absolutely no idea it can be used to prevent the HHH000104 Hibernate issues.
As previously explained, if you want to overcome the “HHH000104: firstResult/maxResults specified with collection fetch; applying in memory!” issue, you have to either use 2 queries or a window function to fetch and limit the number of parent records while making sure you always fetch all their associated child entities.
Even if the HHH000104 issue is logged as a warning message, it might pass unnoticed when the amount of data is fairly low, only to become a significant performance issue when data starts accumulating.
In this article, I’m going to explain why you should always activate the hibernate.query.fail_on_pagination_over_collection_fetch configuration property and, instead of a warning message, you will get an exception that’s unlikely to go unnoticed.
How to expose Hibernate Statistics via JMX
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
Introduction
As already explained, Hibernate provides a very flexible statistics mechanism. The Hibernate metrics can be accessed either programmatically via the org.hibernate.stat.Statistics interface or via JMX (Java Management Extensions).
In this article, you are going to see how you can expose the Hibernate statistics metrics using JMX.
How to expose Hibernate Statistics via #Java Management Extensionshttps://t.co/1LfJcWYvHU pic.twitter.com/cam2NhCw47
— Java (@java) May 9, 2019
