The "session.load(Person.class, 2)" thing is not done normally. It is not even p... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		watwut on April 12, 2021 \| parent \| context \| favorite \| on: Problems with JPA/Hibernate The "session.load(Person.class, 2)" thing is not done normally. It is not even part of JPA. It is hibernate only feature. So in all project I have seen, calling setter did not changed database. > Do you mean that people normally call update or merge to persist an Entity? Yes, people normally call update and merge to persist an entity.

alserio on April 12, 2021 [–]

People normally do that when they do not have to do that.

  Dog rex = em.find(Dog.class,"rex"); // 1
  rex.setAge(2); // 2
  // other query // 3

At 3 the update is flushed on the underlying db. This is pure JPA. Calling merge is forcing an useless query before the update. Also, merge returns the managed entity.

Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact