Fix CLI --execute {file}.sql option to support CRLF line break, #519
Conversation
This file contains 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
Replace ";\n" to ";" in --execute line splitting.
Codecov Report
@@ Coverage Diff @@
## main #519 +/- ##
=======================================
Coverage 92.53% 92.53%
=======================================
Files 173 173
Lines 10925 10925
=======================================
Hits 10109 10109
Misses 816 816 Continue to review full report at Codecov.
|
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.
Replace ";\n" to ";" in --execute line splitting.
SQL files which are generated in Windows OS usually use CRLF symbol for line-break.
Current CLI
--executeoption was handling only the first statement and ignores the remainders.Fix splitting symbol not to contain
\nto resolve this issue.