Allow using JSON path in select results #189
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.
This closes #187.
Before ClickHouse supported JSON type, the select result should have at most 3 fields(
db.table.column
), so it's good to represent it withColumnIdentifier
.After introducing JSON type, the JSON path might have more 3 levels, and it's weird
to represent the JSON path with
db.table.column
. So this PR introducesPath
for thispurpose. And yes, it will break user behaviors if using
ColumnIdentifier
.