borinquenkid commented on PR #16701: URL: https://github.com/apache/grails-core/pull/16701#issuecomment-6379239565
Pushed 1cbfaecc4c. Since the last round: - A shared join table with one key column and an element column per association failed on Oracle (ORA-00001 on the second association); the Oracle key now takes the columns of every association that shares a column with it. runs that mapping on H2, PostgreSQL, MySQL, MariaDB and Oracle and failed on Oracle before. - Each collection of a shared table is restricted to its own rows, so clearing one association keeps the other. - The 8.0.0 constructor of and the deprecated on the three passes are kept. - The duplicate-row cases now also duplicate a row of the second association; with the per-association key removed they fail on all five databases, where before only Oracle did. Three things found while testing are not fixed here and are tracked: removing one element of a set deletes every row of the association for the owner, shared table or not, also on the base of this PR (#16745; three pending features pin it), DB2's unique index null semantics are unverified (#16746), and `is empty` / `is not empty` on an association that shares a key column also sees the rows of the other one, which the restriction does not reach (#16748; one pending feature). A set cannot share a join table with a list or a map, since the list's index column is not null; the binder's javadoc says so. -- 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]
