ByThorben JanssenIn the real world, most objects have a natural identifier. Typical examples are the ISBN number of a book, a company’s tax identifier or a person’s social security number. You could, of course, use these identifiers as primary keys. But most often, it’s a better idea to generate numeric, surrogate keys. They are easier to…
ByThorben JanssenHibernate 5.2 introduced several changes based on Java 8 features. In previous posts, I showed you how to get query results as a Stream and the support of DateTime API classes and Optional. In this post, I will have a look at a small change to some Hibernate annotations. Some of them are now @Repeatable…
ByThorben JanssenJava 8 introduced Optional<T> as a container object which may contain null values. It’s often used to indicate to a caller that a value might be null and that it need to be handled to avoid NullPointerExceptions. Sounds pretty useful, right? So why not use them in your persistence layer for optional entity attributes or…
ByThorben JanssenSince version 5.2, Hibernate starts to use Java 8 classes in their proprietary APIs. The JPA standard will most likely do the same with version 2.2, but who knows when we will get that. Until then, Hibernate’s proprietary APIs are all we have, and I will present the most interesting changes here on the blog….
ByThorben JanssenIt happens quite often that you have to load multiple entities by their primary keys. And new developers are often surprised when they learn that JPA and Hibernate versions before 5.1 do not offer a simple API for it. With JPA and older Hibernate versions, you have 2 options to fetch multiple entities from the database: You…