Changed vector of SetOperations to SetOperation pointer#199
Closed
Changed vector of SetOperations to SetOperation pointer#199
Conversation
Contributor
Author
|
We should add test cases with nested SQL statements where a nested statement contains (a) set operation(s). |
Contributor
|
I think, we need the vector. (see my comments at #138) |
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.
As mentioned by @Daniel-Xu (see #138 (comment)), the vector
SelectStatement::setOperationsnever contains more than one element. Therefore, using a pointer instead of a vector is sufficient.