Database trigger and Hibernate

Question

I've met a scenario:

save or update some data in a target table by hibernate
there is a trigger on the target table which will be executed before insert or update operations of the target table
select out this record by hibernate

But I find that the fields which have been modified by the trigger are not really fetched out. Is this related with transactions commit of Hibernate (flush() has already be called) or Hibernate cache? thanks.

Stefan Steinegger · Accepted Answer · 2011-08-08 14:11:16Z

9

You can map properties as generated values. These values always come from the database and can't be stored. Hibernate automatically loads these values in a subsequent query after inserting or updating the database.

answered Aug 8, 2011 at 14:11

Stefan Steinegger

64.8k17 gold badges132 silver badges193 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Augusto · Accepted Answer · 2011-08-08 11:13:08Z

5

This can be caused by both the first (session) or second (e.g. ehcache) caches. To re-read the entity, you'll need to call session.refresh().

From hibernate docs (at the bottom of the section)

It is possible to re-load an object and all its collections at any time, using the refresh() method. This is useful when database triggers are used to initialize some of the properties of the object.

sess.save(cat);
sess.flush(); //force the SQL INSERT
sess.refresh(cat); //re-read the state (after the trigger executes)

answered Aug 8, 2011 at 11:13

Augusto

30.2k6 gold badges66 silver badges98 bronze badges

Collectives™ on Stack Overflow

Database trigger and Hibernate

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related