ByThorben JanssenDefining a static named query via the @NamedQuery annotation is the most common way in JPA. It has the main advantage that the persistence provider can compile and validate the query at start-up time. But you also have to define the query statically at compile time. OK, you can still define a dynamic query at runtime but how do you…
ByThorben JanssenWhen you write a criteria query or create a dynamic entity graph, you need to reference the entity classes and their attributes. The quickest and easiest way is to provide the required names as Strings. But this has several drawbacks, e.g. you have to remember or look-up all the names of the entity attributes when you write the query….
ByThorben JanssenYour entity classes map a database schema, which must be created before or during application startup. You can do this in various ways. You can run your own scripts, use tools like Flyway or Liquibase, or use the schema generation feature defined by the Jakarta Persistence specification (JPA). In this article, you will learn how…
ByThorben JanssenUp to Version 2.1, JPA was missing real support for stored procedures. The only available option was to use a native query. This changed with JPA 2.1, when @NamedStoredProcedureQuery and StoredProcedureQuery were introduced as two of the new features. I wrote about @NamedStoredProcedureQuery and how to use it to define stored procedure calls in the…
ByThorben JanssenUsing stored procedures to implement parts of the application logic in the database is a widely used approach in huge, data-heavy applications. Nevertheless, there was no good support for them before JPA 2.1. You had to use a native query, to call the stored procedure in the database. Since the JPA 2.1 release, JPA supports two different…