Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
In this article, we are going to see what JPA query hints are, and get to know all the query hints supported by Hibernate.
Understanding the Hibernate query hints is very important when developing a non-trivial enterprise application since they allow you to customize the way queries are executed by Hibernate.
A beginner’s guide to JPA and Hibernate query hints @vlad_mihalceahttps://t.co/9V7UcuBQ7C pic.twitter.com/LugFjLoWxt
— Java (@java) June 27, 2019
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
In this article, we are going to see what is the best way to map the entity version property with JPA and Hibernate.
Most often, we overlook the basic entity type mappings, focusing more on associations or querying options. However, basic types can also have a significant impact on application performance, especially if the type in question is used in many entity mappings.
The best way to map an entity version property with JPA and Hibernate with @vlad_mihalcea https://t.co/EoKKHozMf8 pic.twitter.com/kgL08pgtOB
— Java (@java) June 19, 2019
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
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
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
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.
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
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.
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
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.
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
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
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
Hibernate provides a very powerful Statistics mechanism that, unfortunately, is lesser known. In this article, we are going to see how the Hibernate Statistics mechanism works, and how you can activate.
While the Hibernate Statistics mechanism is not enabled by default, you will see that many applications can benefit from using it, especially when it comes to determining cache effectiveness.
A beginner’s guide to Hibernate Statistics@vlad_mihalcea https://t.co/OdUcM0A74x pic.twitter.com/CNajj2H9xj
— Java (@java) May 1, 2019
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
In a relational database, a relationship is formed by correlating rows belonging to different tables. A table relationship is established when a child table defines a Foreign Key column that references the Primary Key column of its parent table.
Every database table relationship is, therefore, built on top of Foreign Key columns, and there can be three table relationship types:
In this article, we are going to describe all these three table relationships as well as their use cases.
A beginner’s guide to database table relationships@vlad_mihalceahttps://t.co/84cgiDkUhc pic.twitter.com/51qbRUlEQ6
— Java (@java) April 24, 2019
Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. Hypersistence Optimizer is that tool!
In this article, we are going to see how we can implement a database job queue using SKIP LOCKED.
I decided to write this article while answering this Stack Overflow question asked by Rafael Winterhalter.
Since SKIP LOCKED is a lesser-known SQL feature, it’s a good opportunity to show you how to use it and why you should employ it, especially when implementing a job queue task.
How to implement a database job queue using SKIP LOCKED.@vlad_mihalcea https://t.co/sX2bkCXeHk pic.twitter.com/mg5WzOax0w
— Java (@java) April 17, 2019
