[
https://issues.apache.org/jira/browse/CASSANDRA-12189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384129#comment-15384129
]
Alex Petrov commented on CASSANDRA-12189:
-----------------------------------------
True. As it's always ambiguous: one can always supply the correct end delimiter
on the next line, therefore it's indistiguishable, and limiting it to the
single line would not be a good behaviour.
I'm +1 on this.
I've tried to rebase it on top of trunk and it merges clearly.
> $$ escaped string literals are not handled correctly in cqlsh
> -------------------------------------------------------------
>
> Key: CASSANDRA-12189
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12189
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Mike Adamson
> Assignee: Mike Adamson
> Fix For: 3.x
>
>
> The syntax rules for pg ($$) escaped string literals in cqlsh do not match
> the lexer rule for this type in Lexer.g.
> The {{unclosedPgString}} rule is not correctly matching pg string literals in
> multi-line statements so:
> {noformat}
> INSERT INTO test.test (id) values (
> ...$$<xml/>
> {noformat}
> fails with a syntax error at the forward slash.
> Both {{pgStringLiteral}} and {{unclosedPgString}} fail with the following
> string
> {noformat}
> $$a$b$$
> {noformat}
> where this is allowed by the CQL lexer rule.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
