borinquenkid commented on PR #16532: URL: https://github.com/apache/grails-core/pull/16532#issuecomment-6297013501
Thanks @jdaugherty. All three in 337f3165ad, and the base is `8.0.x` again. 1. **Base.** Moved back to `8.0.x`; you're right that the warning belongs on the oldest branch with the defect and merges up from there, with the startup failure matrei suggested staying a separate `9.0.x` change. The branch still merges cleanly there, and this push gives it a run against the `8.0.x` merge. 2. **"They hold no rows".** The sentence now distinguishes the two cases: in a schema Hibernate 7 created the tables hold no rows, so drop them and let GORM recreate them (or migrate); an application that moves from Hibernate 5 arrives with rows in both tables, because Hibernate 5 stores this shape without `belongsTo`, and is told to migrate those tables rather than drop them. 3. **The `Map` sentence** now sits right after the WARNING admonition. The paragraph that follows it opens "The warning also applies to a many-to-many between a class and itself", so its referent stays the warning rather than the `Map` note. Docs only, no code change since 8ca766e5a5. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
