* fix(database): group root order fields for relation filters on all dialects
PostgreSQL only allows ungrouped root ORDER BY columns when the grouped id
is a real primary key constraint. External tables or views without one
failed with "must appear in the GROUP BY clause" when filtering by a
to-many relation and sorting by a root field.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(database): use snake_case join columns for underscored test runs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(database): prepare schema before creating unconstrained tables
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The v2 field form preset `source` to the current collection for relation fields,
and since #10521 it is submitted with the rest of the form values. The database
reads `source` as `collection.field` of an inherited view field, so these relation
fields were skipped when loading collections and never showed up in v2 blocks.
Add a migration in plugin-field-m2m-array that removes the self source from
belongs-to-array fields whose foreign key array is valid, so already affected
many-to-many (array) fields load again after upgrading.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The v1 admin layout derived its designable state from flowSettings.enabled while
also disabling flow settings on mobile, so widening the window back to desktop
never re-enabled them. Derive designable from the UI Editor switch instead, and
mirror the non-reactive isMobileLayout in state so the layout re-renders when
ProLayout's mobile state changes.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
nocobase[bot]