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.
Please, review the changes, further directions required.
At the point this change will fix error from #26
But another error comes out
Following changes done in own commit being negotiable.
It looks like the only way to proceed is to pass tables used from top level here and join with ones parsed in
validateSelectStmt(...)
The first thing that comes to my mind is to add top-level used tables to
VetContext
It will go down through all the select statements in hierarchy. In order this to work properly used tables may be collected in
ParsedResult
.Not much of test cases available in the project so maybe someone could point to the possible pitfalls of such decision.