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
{{ message }}
Repository navigation
Commit c79eb9c
Browse filesBrowse the repository at this point in the historyBrowse files
test(driver-sql): pin the three-state collision routing on Postgres and MySQL shapes (#5495)
The SQLite tests cover the path end to end, but SQLite is the one dialect
where the decision is easy. Postgres names a column in its DETAIL line
(state 1/2) or a composite (state 3); MySQL names only an index and so can
only ever reach state 3 — which means on MySQL the data probe is not a
fallback, it is the whole mechanism.
This package's unit suite boots SQLite only, so the shapes are injected
rather than driven through live servers — same method and same reason as
sql-driver-unique-violation-predicate.test.ts. The state-2 case asserts the
part that matters most: a named column that is not ours ends the matter
WITHOUT probing, even when the probe would have said yes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015XLbsWE5G58ybd1Leq6bNg
0 commit comments