GH-47713: [C++][FlightRPC] ODBC return number of affected rows#48037
Merged
lidavidm merged 1 commit intoapache:mainfrom Dec 8, 2025
Merged
GH-47713: [C++][FlightRPC] ODBC return number of affected rows#48037lidavidm merged 1 commit intoapache:mainfrom
lidavidm merged 1 commit intoapache:mainfrom
Conversation
github-actions
bot
added
Component: C++
Component: FlightRPC
awaiting review
alinaliBQ
force-pushed
the
gh-47713-sql-row-count
branch
from
4fcdc67 to
2120315
Compare
alinaliBQ
changed the title
Collaborator
Author
|
@lidavidm this draft PR is ready for review! Please have a look |
lidavidm
approved these changes
Nov 28, 2025
github-actions
bot
added
awaiting merge
alinaliBQ
force-pushed
the
gh-47713-sql-row-count
branch
from
2120315 to
67db4e7
Compare
lidavidm
reviewed
Dec 4, 2025
| CheckStringColumnW(this->stmt, 2, L"One"); | ||
| CheckIntColumn(this->stmt, 3, 3); | ||
|
|
||
| ASSERT_EQ(SQL_SUCCESS, SQLRowCount(this->stmt, 0)); |
Member
There was a problem hiding this comment.
nit, but can we write nullptr for nullptr and not use 0?
github-actions
bot
added
awaiting changes
alinaliBQ
force-pushed
the
gh-47713-sql-row-count
branch
from
67db4e7 to
b22c359
Compare
github-actions
bot
added
awaiting change review
Update doc Co-Authored-By: alinalibq <alina.li@improving.com>
alinaliBQ
force-pushed
the
gh-47713-sql-row-count
branch
from
b22c359 to
aed5b0e
Compare
lidavidm
approved these changes
Dec 8, 2025
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 082377a. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 5 possible false positives for unstable benchmarks that are known to sometimes produce them. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this change
Make ODBC return number of affected rows as -1 which to BI tools means number of affected rows is unknown. This is because ODBC only supports
selectstatement and doesn't support queries that affect rows.What changes are included in this PR?
Are these changes tested?
Tested locally on MSVC
Are there any user-facing changes?
N/A