planner: add basic support for column privilege #15
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.
What problem does this PR solve?
Some tiny changes to support column level privilege.
What is changed and how it works?
In the old code,
addVisitInfo
is add in thebuildDataSource
, there is no column information there.To support column privilege, the visited column information must be accurate.
So
addVisitInfo
is moved frombuildDataSource
tobuildProjection
where the column is available.In
buildUpdate
, the column is set foraddVisitInfo
.Check List
Tests
Side effects