Scope. Make the new role column non-null. Schema-only.
Acceptance criteria
Cross-table consistency between role and Account.admin_id continues to rest on the service-layer validation shipped in Phase 1 (Postgres CHECK can't span tables declaratively, and the column is being dropped in Phase 6 anyway, so a trigger isn't worth the trouble).
References. RFC §Phase 2, parent #6646. Depends on #11398.
Scope. Make the new role column non-null. Schema-only.
Acceptance criteria
ALTER TABLE user_organizations ALTER COLUMN role SET NOT NULL, shipped after Phase 1 has fully deployed and every row has a value.Cross-table consistency between
roleandAccount.admin_idcontinues to rest on the service-layer validation shipped in Phase 1 (Postgres CHECK can't span tables declaratively, and the column is being dropped in Phase 6 anyway, so a trigger isn't worth the trouble).References. RFC §Phase 2, parent #6646. Depends on #11398.