(grails-core) 07/16: docs: refresh the native binding schema comparison after closing three refused mappings

[bo...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

borinquenkid pushed a commit to branch 9.0.x-h7-improvement-phase3
in repository https://gitbox.apache.org/repos/asf/grails-core.git

commit d39f374d6f4e1a2d42b6d67821edc1d429233328
Author: Walter Duque de Estrada <wb...@mac.com>
AuthorDate: Wed Oct 7 21:36:27 2026 -0500

    docs: refresh the native binding schema comparison after closing three refused mappings
    
    The comparison now covers 663 groups and native binding refuses 12; the two differences of the
    binder that the closed mappings add (no key for a unique group on a collection, no index named
    after a closure) are listed in the schema table.
    
    Co-Authored-By: Claude Sonnet 5.5 <no...@anthropic.com>
---
 .../asciidoc/advancedGORMFeatures/nativeDomainBinding.adoc     | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/grails-data-hibernate7/docs/src/docs/asciidoc/advancedGORMFeatures/nativeDomainBinding.adoc b/grails-data-hibernate7/docs/src/docs/asciidoc/advancedGORMFeatures/nativeDomainBinding.adoc
index 41a8ca0019..d674f4465c 100644
--- a/grails-data-hibernate7/docs/src/docs/asciidoc/advancedGORMFeatures/nativeDomainBinding.adoc
+++ b/grails-data-hibernate7/docs/src/docs/asciidoc/advancedGORMFeatures/nativeDomainBinding.adoc
@@ -167,7 +167,7 @@ Some bugs of classic binding are not copied by native binding. Native binding do
 [[nativeDomainBinding-schema]]
 === Differences in the Schema
 
-The schema of 620 groups of related domain classes was created with both bindings on H2 and compared: tables, columns with type, nullability, default, length, precision and scale, primary keys with their column order, foreign keys, unique keys, indexes, check constraints and sequences. Apart from the 22 groups that native binding refuses, these are the differences. Other databases are not covered by this comparison, so verify against your own database as described below.
+The schema of 663 groups of related domain classes was created with both bindings on H2 and compared: tables, columns with type, nullability, default, length, precision and scale, primary keys with their column order, foreign keys, unique keys, indexes, check constraints and sequences. Apart from the 12 groups that native binding refuses, these are the differences. Other databases are not covered by this comparison, so verify against your own database as described below.
 
 [cols="2,3,3", options="header"]
 |===
@@ -206,6 +206,14 @@ The schema of 620 groups of related domain classes was created with both binding
 | A unique constraint over the columns of a `unique` group that includes an enum.
 | See <<nativeDomainBinding-behavior,Differences in Behavior>>.
 | `update` adds the constraint.
+
+| No unique key on the table of a collection for a `unique` group mapped on the collection property.
+| See <<nativeDomainBinding-behavior,Differences in Behavior>>.
+| The key never existed in a database created by classic binding: the statement that creates it fails.
+
+| No index named after a closure on the table of a collection whose `index` is a closure.
+| See <<nativeDomainBinding-behavior,Differences in Behavior>>.
+| A database created by classic binding has an index with a name that depends on the start it was created in. Drop it if you want to be rid of it.
 |===
 
 The comparison finds no difference in the unique keys, indexes and identifier columns that natural ids, `unique` groups and `index` options create: they have the same columns in the same order as with classic binding.