ByThorben JanssenOne of the benefits of using JPA and Hibernate is that it provides an abstraction of database-specific dialects and features. So, in theory, you can implement an application, connect it to one of the supported databases and it will run without any code changes. Hibernate does that really well. But let’s be honest, you didn’t…
ByThorben JanssenPostgreSQL is one of the most popular relational databases, and Hibernate is probably the most popular JPA implementation. So, it’s no surprise that they’re often used together and that you don’t have to expect any major issues doing that. But as so often, there is a difference between “it works” and “it works great”. Out…
ByThorben JanssenAssociation mappings are one of the key features of JPA and Hibernate. They model the relationship between two database tables as attributes in your domain model. That allows you to easily navigate the associations in your domain model and JPQL or Criteria queries. JPA and Hibernate support the same associations as you know from your…
ByThorben JanssenJPQL is a powerful query language that allows you to define database queries based on your entity model. Its structure and syntax are very similar to SQL. But there is an important difference that I want to point out before I walk you through the different parts of a JPQL query. JPQL uses the entity…
ByThorben JanssenThis post was originally published on sitepoint’s Java channel: 5 Reasons to Use JPA / Hibernate. Before we dive into the reasons to use JPA, let me quickly explain what it is. The Java Persistence API (JPA) is a specification for object-relational mapping in Java. As for most standards within the Java Community Process, it…