Default serialize optional_idx, add skip_default option to json_serialize_sql()
#11405
+46
−15
Conversation
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
…aults in json_serialize_sql()
|
Thanks! LGTM. We do serialize |
github-actions bot
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Mar 30, 2024
Merge pull request duckdb/duckdb#11405 from Maxxen/more-serialization
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 makes it possible to avoid getting crazy query locations from e.g. empty refs - if you can live with stripping the parse tree from other default values.
Not sure if this breaks forwards-compatability given that empty query locations aren't serialized anymore in the binary serialization, but I don't think we binary serialize parse trees anyway?