BUGFIX: use correct quotes for character escape sequences #41
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
Character escape sequences should be enclosed in double quotes. Otherwise the literal characters t, n, r, 0, x, B will be stripped from the input. The SqLiteIndex already implements this behavior correctly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Character escape sequences should be enclosed in double quotes. Otherwise the literal characters t, n, r, 0, x, B will be stripped from the input.
The SqLiteIndex already implements this behavior correctly.
I encountered the problem with an argument list ending in 0, where
:arg40was trimmed to:arg4which of course had the wrong value.The same might happen for column names when unlucky.