-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*: refactor ExecuteInternal to return single resultset #22546
*: refactor ExecuteInternal to return single resultset #22546
Conversation
Interesting. It looks like this breaks the API used by plugins. It might require some more thought on how/when to break it. |
/run-build enterprise-plugin=pr/39 |
/run-all-tests enterprise-plugin=pr/39 |
e943f72
to
f9eea80
Compare
/run-all-tests |
/run-all-tests |
/run-tics-test |
I've simplified this to only clean up PTAL @tiancaiamao @xhebox |
LGTM |
/merge |
/run-all-tests |
@morgo merge failed. |
/run-tics-test |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-4.0 in PR #22640 |
cherry pick to release-5.0-rc in PR #22655 |
Signed-off-by: ti-srebot <[email protected]>
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-3.0 in PR #22712 |
Signed-off-by: ti-srebot <[email protected]>
What problem does this PR solve?
Problem Summary:
Both
Execute
andExecuteInternal
no longer permit multi-statement, but the return type was maintained the same for backward compatibility.This changes
ExecuteInternal
to return a single result-set.Update: I've removed
Execute
from this PR, we can handle it in followup PRs.What is changed and how it works?
What's Changed:
This changes the return type of
ExecuteInternal
to be a non-array value.All uses of(for future PRs - it does not need to be handled all at once).Execute
are changed to useExecuteInternal
Related changes
Check List
Tests
Side effects
Release note