-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SubSelectFetchTest fails #1502
Comments
It only fetches one association and not all of them as expected
So I've tested reactive 1.1 version of In our current reactive I ran the equivalent tests and they both return one concrete entity (Node) and one that is a Was this change expected? |
So I created/ran .. basically, our reactive test over in ORM test suite. The second result in the result list is a Note that in our test, I can make it work by calling |
Appears that the generated select + subselect query we used in HR 1.1 is not getting generated correctly in HR 2.x which doesn't load the collections in the primary/parent node. see: SqlClientConnection.selectQuery(..) OLD SQL : with paramValues array is EMPTY)
NEW SQL: with paramValues array has one value of '1')
If I intercept the generated SQL and replace the string with the following and remove the '1' parameter, then this test succeeds.
So there's a step or 2 missing in the 'select' sql generation for this use-case. |
@davide In our 6.2.7 ORM version, the SubselectLoader isn't being set. Looks like there was some work done on the SubselectLoader logic in AbstractCollectionPersister.resolveSubselectLoader() in the main branch that may have fixed this. |
This test has never worked since we upgraded to ORM 6. In Hibernate Reactive we extend the subclasses of I think you should check which implementation of What we know at the moment is that this works in Hibernate ORM (we already tested this in the past), and that the test we have in Hibernate Reactive is correct (it was working with ORM 5 and shouldn't require any changes to fix this issue). |
PR merged in ORM's 6.2 branch |
I'm going to reopen this until we upgrade to the next ORM 6.2. But there is no more work needed from our side to fix this issue |
This issue has been fixed for Hibernate Reactive 2.0, but it won't work in 2.1 |
This was fix by a change in Hibernate ORM 6.2.8.Final See https://hibernate.atlassian.net/browse/HHH-17130
This was fix by a change in Hibernate ORM 6.2.8.Final. See https://hibernate.atlassian.net/browse/HHH-17130
The upgrade to Hibernate ORM 6.2.8.Final fixes this issue. See https://hibernate.atlassian.net/browse/HHH-17130
The upgrade to Hibernate ORM 6.2.8.Final fixes this issue. See https://hibernate.atlassian.net/browse/HHH-17130
This reverts commit fc23d87. Something has changed in Hibrnate ORM 6.3 and the previous fix is not enough anymore
This reverts commit fc23d87. Something has changed in Hibrnate ORM 6.3 and the previous fix is not enough anymore
It only load the fetched collection and not all the associations that are part of the entity.
See
hibernate-reactive/hibernate-reactive-core/src/test/java/org/hibernate/reactive/SubselectFetchTest.java
Line 40 in 21e2c2a
The text was updated successfully, but these errors were encountered: