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 ec06096
Browse filesBrowse the repository at this point in the historyBrowse files
[feature](arrow-flight) Let the schema session option put the session back into no database
GetSessionOptions reports a session that is in no database -- the state
it starts in and SWITCH puts it back into -- as schema = "", but that
value could not be set back: SetSessionOptions refused the empty string
and the empty value alike with INVALID_VALUE. The empty value is Flight's
way of unsetting an option and what the ADBC driver sends on its erase
path (adbc.flight.sql.session.optionerase.schema), and no statement leads
to that state, there being no USE of nothing.
Both now put the session back into no database, through a new
ConnectContext.clearDatabase() (which SWITCH shares), without running a
statement: there is nothing in it to check. catalog keeps refusing the
empty value, a session always being in some catalog.
Tests: FlightSessionOptionsTest.testTheEmptyValueOrStringLeavesTheDatabase
(erase, the "" round trip, a user without privileges) and a step of the
test_session_options regression suite (a statement needs a database again
after the clear).
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01Ja986K4PEm2LD8u44L9jd2
0 commit comments