跳至主要内容

JPA 2.1: Bulk Update and Delete


JPA 2.1: Bulk Update and Delete

In the JPA 2.0 and early version, if you want to execute a bulk updating query, you have to use update or delete clause in JPQL directly. JPA 2.1 introduce new Criteria API for updating and deleting.

Post entity

Reuse the Post entity class as example. Add an extra boolean approved property.
In this example, the bulk update operation will set the approved value to true.
@Entity
@Table(name="POSTS")
public class Post implements Serializable {
 
     private boolean approved = false;
}

Criteria Update and Delete API

In JPA 2.1, new CriteriaUpdate and CriteriaDelete are introduced in Criteria API for updating and deleting. The usage is very simple.
The CriteriaUpdate example.
CriteriaBuilder cb = em.getCriteriaBuilder();
CriteriaUpdate<Post> q = cb.createCriteriaUpdate(Post.class);
Root<Post> root = q.from(Post.class);
q.set(root.get("approved"), true)
 .where(root.get("id").in(getCheckedList()));

int result = em.createQuery(q).executeUpdate();
log.info("update @" + result);
The CriteriaDelete example.
CriteriaBuilder cb = em.getCriteriaBuilder();
CriteriaDelete<Post> q = cb.createCriteriaDelete(Post.class);
Root<Post> root = q.from(Post.class);
q.where(root.get("id").in(checkedList));

int result = em.createQuery(q).executeUpdate();
log.info("delete @" + result);
The checkedList value is from checkbox values from JSF UI.

Summary

This feature is a small improvement to JPA API. If you are stick on the type-safe JPA metadata API for JPA programming, it is a big step.
The sample codes are hosted on my github.com account, check out and play it yourself.
When you run the project(jpa-bulk) on Glassfish 4.0 and you could get an exception.
java.lang.RuntimeException: unable to create policy context directory.
There is a known issue in Glassfish 4.0, the fix should be included in the next release. I am using a Nightly version to overcome this barrier temporarily.
发表评论

此博客中的热门博文

JPA 2.1: Attribute Converter

JPA 2.1: Attribute Converter If you are using Hibernate, and want a customized type is supported in your Entity class, you could have to write a custom Hibernate Type. JPA 2.1 brings a new feature named attribute converter, which can help you convert your custom class type to JPA supported type. Create an Entity Reuse thePostentity class as example. @Entity @Table(name="POSTS") public class Post implements Serializable { private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name="ID") private Long id; @Column(name="TITLE") private String title; @Column(name="BODY") private String body; @Temporal(javax.persistence.TemporalType.DATE) @Column(name="CREATED") private Date created; @Column(name="TAGS") private List<String> tags=new ArrayList<>(); } Create an attribute converter In this example…

Auditing with Hibernate Envers

Auditing with Hibernate Envers The approaches provided in JPA lifecyle hook and Spring Data auditing only track the creation and last modification info of an Entity, but all the modification history are not tracked. Hibernate Envers fills the blank table. Since Hibernate 3.5, Envers is part of Hibernate core project. Configuration Configure Hibernate Envers in your project is very simple, just need to addhibernate-enversas project dependency. <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-envers</artifactId> </dependency> Done. No need extra Event listeners configuration as the early version. Basic Usage Hibernate Envers provides a simple@Auditedannotation, you can place it on an Entity class or property of an Entity. @Audited private String description; If@Auditedannotation is placed on a property, this property can be tracked.

Spring Data Mongo: bridge MongoDB and Spring

Spring Data Mongo: bridge MongoDB and SpringMongoDBis one of the most popular NoSQL products, Spring Data Mongo(Maven archetype id is spring-data-mongodb) tries to provides a simple approach to access MongoDB. Configuration Add the following code fragments in your Spring configuration. <!-- Mongo config --> <mongo:db-factory id="mongoDbFactory" host="localhost" port="27017" dbname="conference-db" /> <bean id="mongoTemplate" class="org.springframework.data.mongodb.core.MongoTemplate"> <constructor-arg ref="mongoDbFactory" /> </bean> <mongo:repositories base-package="com.hantsylabs.example.spring.mongo" /> Firstly, declare aDbFactorywhich is responsible for connecting to the MongoDB server. Then, register theMongoTemplateobject which envelop the data operations on MongoDB. Lastly addmongo:repositorieswith an essentialbase-packageattribute, Spring will discovery your d…