DBSQLOperation Refactoring (1 of 3) #163
Merged
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.
Currently we have
DBSQLOperation
implemented as a main class + several helpers that implement various suboperations. Initially this approach helped during implementing DirectResults and other features, but as we go further it becomes harder to maintain relations between those helpers. After weighing all the pros and cons, I decided to move code from helpers to mainDBSQLOperation
class. This PR gets rid ofCompleteOperationHelper
andSchemaHelper
(one commit per each helper, so for better understanding comits may be reviewed one-by-one), and following PRs will do the same for other helpers.