Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

JPA - saving changes without persist() invoked

We are using Toplink implementation of JPA + Spring + EJB. In one of our EJBs we have something like this:

public void updateUser(long userId, String newName){
    User u = em.get(User.class, userId);
    u.setName(newName);
    // no persist is invoked here
}

So, basically this updateUser() method is supposed to update the name of a user with the given userId. But the author of this method forgot to invoke em.persist(u).

And the strangest thing is that it works fine. How can it be? I was 100% sure that without invoking em.persist() or em.merge() there is no way that changes could have been saved into database. Could they? Is there any scenario when this could happen?

like image 292
anthony Avatar asked Nov 23 '09 18:11

anthony


People also ask

How do I save and update in JPA?

You can choose between JPA's persist and merge and Hibernate's save and update methods. It seems like there are 2 pairs of 2 methods that do the same. You can use the methods persist and save to store a new entity and the methods merge and update to store the changes of a detached entity in the database.

Does Hibernate automatically update changed objects?

Kind of mysterious – all you want to do would be to update the some component on your java logic and it is automatically saved in the database.

What is difference between persist and save in hibernate?

Difference between save and persist method in Hibernate First difference between save and persist is there return type. Similar to save method persist also INSERT records into database but return type of persist is void while return type of save is Serializable object.


1 Answers

You're working with a managed entity. If the entity does not become detached because its entity manager is closed, all changes done to the entity are reflected to the database when the session is flushed/closed and the transaction commited.

From the Java EE tutorial:

The state of persistent entities is synchronized to the database when the transaction with which the entity is associated commits.

Edit for clarity and explanation: So there are three distinct modes that an entity could be in during its lifecycle:

  • Unsaved: The entity has been instantiated, but persist() has not been called yet.
  • Managed: The entity has been persisted using persist(), or loaded from the database, and is associated with an entity manager session. All changes to the entity are reflected to the database when the entity manager session is flushed.
  • Detached: The entity's entity manager session was closed. Changes to the entity will not be reflected to the database automatically, but can be merged explicitly using the merge() command.
like image 137
Henning Avatar answered Jan 03 '23 01:01

Henning