Diego ImbertandClaude Opus 5 8868c5ff72 fix(datatables): nothing is decided before the answer for this data table arrives ...

Starting a new app while the role list loads saved no role, which the server
resolves to the data table's configured default — a role the caller may not be
allowed to use, where a moment later the picker would have chosen one they can.
Start waits for the list that answers for the data table selected.

The schemas and the right to create one get the same stamp the role list has. At
mount they are the initial value rather than an answer, and the effect read that
as "this role cannot create schemas", flipping the modal off `New` with nothing
to put it back; during a switch they are the previous data table's.

A role drop that fails names what it leaves behind whichever statement failed:
the config that stopped naming them has committed either way.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S5arH3G2Sa1Qqm32veJQ1n

2026-09-04 14:41:11 +02:00

..

src

fix(datatables): nothing is decided before the answer for this data table arrives

2026-09-04 14:41:11 +02:00

Cargo.toml

feat: add SQL migrations for data tables (#9693)

2026-07-07 08:25:16 +00:00