Don't accept term command if ';' is EOL but within a quote #20
Comments
m-church
pushed a commit
to cv-library/altsql-shell
that referenced
this issue
May 17, 2017
Introducting a new method in the Model to parse a line from the command prompt and determine whether the command is complete. For example - altsql> select * from film where title = "; "; This failed because it stops at the end of the line even though we are inside quotation marks.
m-church
pushed a commit
to cv-library/altsql-shell
that referenced
this issue
May 17, 2017
Introducting a new method in the Model to parse a line from the command prompt and determine whether the command is complete. For example - altsql> select * from film where title = "; "; This failed because it stops at the end of the line even though we are inside quotation marks.
m-church
pushed a commit
to cv-library/altsql-shell
that referenced
this issue
May 17, 2017
Introducting a new method in the Model to parse a line from the command prompt and determine whether the command is complete. For example - altsql> select * from film where title = "; "; This failed because it stops at the end of the line even though we are inside quotation marks.
m-church
pushed a commit
to cv-library/altsql-shell
that referenced
this issue
May 17, 2017
Introducting a new method in the Model to parse a line from the command prompt and determine whether the command is complete. For example - altsql> select * from film where title = "; "; This failed because it stops at the end of the line even though we are inside quotation marks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This should work:
This means:
select * from film where title = ";\n"We need to look at the buffer and determine if the ';' or '\c' or '\g' is within a quote scope before treating it as an EOL signifier.
The text was updated successfully, but these errors were encountered: