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
ODBC: expose multiple result sets through SQLMoreResults #655
Tracked by #587 and required by the target design in #644.
Scope
Retain every TResultSet returned by TExecuteQueryResult, in server order,
instead of constructing a cursor only for result set zero.
Position an executed statement on the first result and implement SQLMoreResults through normal statement-handle validation.
On advance, discard unread rows from the current result, reset fetch and SQLGetData state, rebuild the implementation row descriptor, and expose
the next result's metadata and row count.
Preserve application column bindings across results. Applications remain
responsible for rebinding when the result shape changes.
Return SQL_NO_DATA after the final result and release the retained result
sequence on close, cancel, re-execution, error, and statement destruction.
Advertise SQL_MULT_RESULT_SETS = "Y" and keep SQLGetFunctions capability
reporting consistent with the implementation.
Define the available SQLRowCount behavior for queries that mix result sets
with DML, using the information exposed by YDB query statistics.
Tests
Native ODBC tests with multiple result sets of different shapes.
Advancing before the current result has been fully fetched.
Descriptor, binding, row-count, and SQLGetData offset transitions.
Empty result sequences, final SQL_NO_DATA, invalid handles, close,
cancellation, and re-execution.
Qt QODBC QSqlQuery::nextResult() and forwardOnlyMultipleResultSet; remove their expected-failure classification.
Acceptance
Every YDB result set is reachable in order through SQLMoreResults, capability
metadata reports support, and the native and Qt multiple-result tests pass.
Activity