We're updating the issue view to help you get more done. 

Auto-flush on JPA native SQL query

Description

We will need to make a slight change to execution of JPA native SQL queries to add an "auto flush".

The problem with this is that, unlike with HQL/JPQL, we do not know the tables affected by a native SQL query (and doing so would be extremely difficult and not worth the effort). Historically, Hibernate users would have relied on the addSynchronizedQuerySpace/addSynchronizedEntityName methods of org.hibernate.SQLQuery to indicate the tables needing flushed. JPA however has no such notion.

As I see it, I think the change here needs to be to implicitly perform a full flush when a JPA native SQL query is executed where the wrapped/underlying org.hibernate.SQLQuery does not define any "query spaces"; a partial flush just is not possible in that case. That allows us to pass the TCK, but still allows users to set "query spaces" if they wish to do the more efficient partial auto-flush.


For posterity, HEM users can still accomplish this by unwrapping to Hibernate's native org.hibernate.SQLQuery adding to the "synchronized query spaces", like:

1 2 3 Query jpaSqlQuery = entityManager.createNativeQuery( ... ); jpaSqlQuery.unwrap( org.hibernate.SQLQuery.class ).addSynchronizedEntityClass( Person.class ); ...

There are 3 forms of adding "synchronized query spaces":

  • addSynchronizedQuerySpace - Add a table to synchronize on

  • addSynchronizedEntityClass - Add the tables to which the given entity (by class) is mapped

  • addSynchronizedEntityName - Add the tables to which the given entity (by name) is mapped

Environment

None

Status

Assignee

Steve Ebersole

Reporter

Steve Ebersole

Fix versions

Labels

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

4.3.0.Beta3

Priority

Major