You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
control: cover the edge-recon gate in a non-default database
The fix had no test: `plan_needs_implicit_edge_recon` had zero call sites
anywhere in the suite, and the existing non-default-database graph test sends an
expression update that the planner rejects at plan time, so it never reaches
this gate. Reverting the fix left every test green.
Two tests now drive the gate directly: seed a catalog with an edge-bearing
collection in a non-default database, hand the gate a `BulkUpdate` carrying the
database-qualified collection the planner builds, and assert it fires and returns
that qualified key. The second covers `DatabaseId::DEFAULT` as the identity case.
Reverting the bare-name lookup fails the first and leaves the second passing,
which is the red arm this needed.
The restore-path comment also claimed the collection registry qualifies its bare
string before the engine is keyed. It does not: the string reaches
`from_stored` and the tenant engine's collection map verbatim, which is what
makes restore disagree with an ordinary apply. The comment now says that.
0 commit comments