[GH] (grails-core/fix/16659-lazy-many-to-one-fetch-mode): Workflow run "CodeQL" failed!

[GitBox <gi...@apache.org>]

The GitHub Actions job "CodeQL" on grails-core.git/fix/16659-lazy-many-to-one-fetch-mode has failed.
Run started by GitHub user hk2166 (triggered by hk2166).

Head commit for run:
0eae0f410b29f52e0895785d5b57cd7b237310ee / hk2166 <96...@gmail.com>
Fetch a lazy many-to-one with SELECT when no fetch mode is mapped

Without a fetch mapping, ManyToOneValuesBinder bound every many-to-one
with FetchMode.DEFAULT. Hibernate 7 resolves DEFAULT to a JOIN when it
cannot proxy the associated entity, and then logs HHH000510 at startup
for each such association that is lazy, which GORM maps by default.

A lazy many-to-one without a fetch mapping is now bound with
FetchMode.SELECT, the fetch mode that matches lazy loading. Eager
many-to-ones and those with a mapped fetch mode are bound as before.
The same associations are loaded as before: an association to an entity
Hibernate cannot proxy was already loaded together with its owner.

Fixes #16659

Co-Authored-By: Claude Opus 5.5 <no...@anthropic.com>

Report URL: https://github.com/apache/grails-core/actions/runs/39017533328

With regards,
GitHub Actions via GitBox