With the default flush mode Hibernate flushes query regions before queries to run SQL against actual table data.
If two entity are connected using the join table and data is queried using a criteria Hibernate does not flush to the join table.
It flushes to the entity tables though.
The attached test case produces the SQL output
Hibernate: insert into USERS (ID, NAME) values (null, ?)
Hibernate: insert into ITEMS (ID, NAME) values (null, ?)
Hibernate: select this_.ID as ID0_1_, this_.NAME as NAME0_1_, items3_.USER_ID as USER1_, items1_.ID as ITEM2_, items1_.ID as ID2_0_, items1_.NAME as NAME2_0_ from USERS this_ inner join USER_ITEMS items3_ on this_.ID=items3_.USER_ID inner join ITEMS items1_ on items3_.ITEM_ID=items1_.ID where items1_.NAME=?
But it should flush to the USER_ITEMS table before executing the criteria query.
The commented HQL query does flush to both the entity tables and the join table.
The problem is in the org.hibernate.loader.criteria.CriteriaQueryTranslator.getQuerySpaces() method.
It returns only the entity tables.
Hibernate Core 3.3.1.GA, H2 1.1.108
@Etienne Miret, thank you very much. I tested your patch with my test cases and it works fine.
Is there any chance to get it fixed in the next bugfixing version?
@ It’s not my patch, it’s Maxim’s. I only added some tests and created the pull request.
Regarding the inclusion of this fix in the next release, well it depends on when or someone else with write access to the repository will find time to review it. Which can be very long. The current oldest pull request waiting for approval is over one year old.
Given that there's already fixes for this, testcases that show the bug, and it's a pretty major bug, what's the holdup?
Applied PR upstream and on 5.2.