-
Notifications
You must be signed in to change notification settings - Fork 34
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
DBSQLOperation Refactoring (3 of 3) #198
Merged
Merged
Conversation
This file contains 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
…ltsHelper into provider of TRowSet Signed-off-by: Levko Kravets <[email protected]>
…vider interface Signed-off-by: Levko Kravets <[email protected]>
kravets-levko
temporarily deployed
to
azure-prod
October 24, 2023 10:04 — with
GitHub Actions
Inactive
kravets-levko
had a problem deploying
to
azure-prod
October 30, 2023 10:32 — with
GitHub Actions
Failure
Signed-off-by: Levko Kravets <[email protected]>
kravets-levko
force-pushed
the
refactoring-operation-helpers-3
branch
from
October 30, 2023 10:35
4e3d7a4
to
6ada0db
Compare
kravets-levko
had a problem deploying
to
azure-prod
October 30, 2023 10:35 — with
GitHub Actions
Failure
kravets-levko
requested review from
arikfr,
superdupershant,
yunbodeng-db,
susodapop,
nithinkdb and
andrefurlan-db
as code owners
October 30, 2023 10:57
kravets-levko
had a problem deploying
to
azure-prod
October 30, 2023 12:17 — with
GitHub Actions
Failure
kravets-levko
had a problem deploying
to
azure-prod
October 30, 2023 12:19 — with
GitHub Actions
Failure
kravets-levko
had a problem deploying
to
azure-prod
October 31, 2023 18:12 — with
GitHub Actions
Failure
4 tasks
kravets-levko
temporarily deployed
to
azure-prod
November 9, 2023 15:49 — with
GitHub Actions
Inactive
kravets-levko
temporarily deployed
to
azure-prod
November 9, 2023 15:52 — with
GitHub Actions
Inactive
kravets-levko
temporarily deployed
to
azure-prod
November 9, 2023 16:13 — with
GitHub Actions
Inactive
kravets-levko
temporarily deployed
to
azure-prod
November 14, 2023 16:30 — with
GitHub Actions
Inactive
nithinkdb
reviewed
Nov 14, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for doing this!
nithinkdb
approved these changes
Nov 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Continuation of #163 and #185
Modify
FetchResultsHelper
and result handlers so they have unified interface and allow chaining. The idea is to form a sort of pipeline that will fetch operation results and then process it on each step. Currently it's just fetching and preparing (converting to array of rows), but later we'll add an additional step to ensure that chunk size matchesmaxRows
, or steps that may convert data to different representation (or return raw data)