Author: Michael Bouschen
-
JPA Pitfalls (6): Query Result with Duplicates
This blog article is part of a “series of blog articles” about common pitfalls using JPA and ways to avoid them. In this article, we describe unexpected duplicates in the result of a JPQL query.
-
JPA Pitfalls (5): Object-Relational Mapping and Inheritance
This blog article is part of a “series of blog articles” about common pitfalls using JPA and ways to avoid them. In this article, we describe possible performance impacts of JPA inheritance mapping strategies.
-
JPA Pitfalls (4): Relationship Owner
This blog article is part of a “series of blog articles” about common pitfalls using JPA and ways to avoid them. In this article, we describe issues with bidirectional relationships.
-
JPA Pitfalls – a Series of Serious JPA Obstacles
Most of our Java-based web-applications store their data in a relational database such as Oracle, PostgreSQL, MySQL, MariaDB or MS SQLServer. The standard way to access and modify the data is using an object-relational mapping as specified by the Java Persistence API (JPA). Over the years JPA has become a mature specification and there are…
-
New JSR Proposed: JPA 2.1
by
Update 01. Feb 2011 akquinet joins the JSR-338 expert group to take active part in developing the JPA 2.1 specification. A new Java Specification Request JSR-338 has been submitted to extend the Java Persistence API (JPA). The JSR will address a number of features requested by the community: Improvement of the query language and…
You must be logged in to post a comment.