You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/10/05 21:27:41 UTC
[GH] (grails-core/fix/hibernate7-many-to-many-inverse-join-table-8.0.x): Workflow run "Licensing - RAT Report" failed!
The GitHub Actions job "Licensing - RAT Report" on grails-core.git/fix/hibernate7-many-to-many-inverse-join-table-8.0.x has failed.
Run started by GitHub user borinquenkid (triggered by borinquenkid).
Head commit for run:
a227adf0b052d7d4c784428a8ab7a951d069d51d / Walter Duque de Estrada <wb...@mac.com>
fix: inverse side of a many-to-many adopts the owner's join table
The inverse side of a bidirectional many-to-many derived its join table name
and key/column names from its own mapping. When only the owning side configured
joinTable, the owner wrote one table and the inverse side read a different,
default-named one, so rows persisted through the owner were invisible through
the inverse side.
CollectionBinder now lets a non-owning many-to-many without its own join table
name adopt the owner's name, schema and catalog, with key and column swapped
(its key is the owner's column, its column is the owner's key). An inverse side
that names its own join table is left untouched, so mappings that configure both
sides (the documented form) behave as before.
Hibernate 5 (GrailsDomainBinder.calculateTableForMany) has the same
inverse-from-own-mapping lookup, so there both sides had to repeat joinTable;
this makes the owner-only configuration work in Hibernate 7.
Co-Authored-By: Claude Sonnet 5.5 <no...@anthropic.com>
Report URL: https://github.com/apache/grails-core/actions/runs/37366168868
With regards,
GitHub Actions via GitBox