In Relation To

If you want to call SQL functions from the SELECT clause of a JPQL or Criteria API queries, then you should register the function as otherwise, the entity query will not compile. For more details about the best way to register such SQL function, check out this article.

This article shows that collection EAGER fetching can lead to N+1 query problems. However, this can happen not only to entity collections. You can bump into this issue with @ManyToOne or @OneToOne associations as well since they are fetched eagerly by default too. The best way to address the N+1 query issue is to detect it automatically during testing, as explained in this article.

For our Russian readers, there is a very good article on Habr which addresses many topics that are very useful when using JPA and Hibernate.

If you want to customize the default mapping between JPA entities and database columns, you can use a custom naming strategy. This article explains how you can do that with both Hibernate 4 and 5.

If you are using Hazelcast as a Hibernate 2nd-level cache provider, and you are running on Java 10, check out this article for how to set up your project dependencies in Maven so that everything works properly.

The Java Magazine features one article about some design patterns to consider when using JPA and Hibernate.

If you are using Hibernate Validator 6.0, you might want to upgrade to the 6.0.11 version which comes with improved compatibility with JDK 11 and a couple of bug fixes.