Properly escape strings and symbols for ILP format #3
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
jbuckmccready
force-pushed
the
fix_escaping_inputs
branch
from
6e0eef8 to
ee89558
Compare
ultd
approved these changes
Sep 25, 2023
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.
Strings and symbols were not being escaped, this fixes the issue.
Escaping done according to docs here:
strings: https://questdb.io/docs/reference/api/ilp/columnset-types/#string
symbols: https://questdb.io/docs/reference/api/ilp/overview/#symbolset-values
And using this Rust client code as reference:
https://github.com/questdb/c-questdb-client/blob/fa10c59b3086520235b0580afc6ac25648e0f047/questdb-rs/src/ingress/mod.rs#L407-L462