em.createNativeQuery executes first than em.persist and now?

Question

em.createNativeQuery executes first than em.persist and now?

Navigation

#1 by (2 votes)

3

I'm developing an application with Hibernate + Spring mv. spring takes care of EntityManager dependency for my DAO, however I have the following problem.

I persist an object called User
After I run createNativeQuery with "insert into table1 (field1, field2) select field1, field2 from User"

I noticed that in table1 I was not registering the User, I checked to enable show_sql and in the console hibernate first runs the createNativeQuery after the persist, regardless of the order the two were written.

Is there any way to configure hibernate to keep the order?

java spring hibernate

asked by anonymous 08.04.2015 / 06:28

1 answer

JavaScript error when opening page - Uncaught SyntaxError Conversion and grouping of rows in columns dynamically in Oracle

score 2 · Accepted Answer

The problem is caused because many of the common operations are stored in a sort of in-memory queue, which is usually downloaded to the database at one time when closing EntityManager . Hibernate thus tries to optimize access to the database. However, native queries do not go through this queue and for DBMS it is as if the first command had never occurred.

The ideal in this case is to execute the flush() method after the persist() to force that the commands waiting in the queue were sent to the database, in this case the insertion.