The GitHub Actions job "Coverage" on grails-core.git/fix/h7-subquery-alias-correlation-8.0.x has failed. Run started by GitHub user jdaugherty (triggered by jdaugherty).
Head commit for run: 742729dfabc70e07b43b13c8c338a4375d47efe7 / James Daugherty <[email protected]> fix(hibernate7): join a nested createAlias path one association at a time createAlias('owner.address', 'a') passed the whole path to a single JPA join, which takes one attribute, so the query failed with "Could not resolve attribute 'owner.address'". GORM validates such a path as a chain of associations from the queried entity, so ExpressionResolver now joins it one association at a time. The first association shares the join the query already has for it (its first alias, an association block or a dotted property path) and keeps the join type the query gives that association, so adding a left alias on 'favorite.tag' does not turn the inner join of a restriction on 'favorite.label' into a left join. The associations after it use the join type of the alias, as does the first one when nothing else joins it. The path is relative to the root of the query that declares the alias, so a subquery does not pick up the outer query's join. This is the one feature of SubqueryAssociationCorrelationSpec that 8.0.x did not already pass after #16573. The Hibernate 7 guide documents nested alias paths under Association Aliases. Report URL: https://github.com/apache/grails-core/actions/runs/41928098718 With regards, GitHub Actions via GitBox
