[
https://issues.apache.org/jira/browse/CASSANDRA-11456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487016#comment-15487016
]
Maxim Podkolzine commented on CASSANDRA-11456:
----------------------------------------------
[~beobal] Oh, it's so unfortunate.
We're currently using 3.5, have tried 3.7 and it turned out to be slower. So
we're evaluating 3.6 and probably will stick with that.
But in case it fails, I don't see any workaround to construct a LIKE constraint
in 3.5 with the query builder.
> support for PreparedStatement with LIKE
> ---------------------------------------
>
> Key: CASSANDRA-11456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11456
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL
> Reporter: Pavel Yaskevich
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Labels: sasi
> Fix For: 3.6
>
>
> Using the Java driver for example:
> {code}
> PreparedStatement pst = session.prepare("select * from test.users where
> first_name LIKE ?");
> BoundStatement bs = pst.bind("Jon%");
> {code}
> The first line fails with {{SyntaxError: line 1:47 mismatched input '?'
> expecting STRING_LITERAL}} (which makes sense since it's how it's declared in
> the grammar). Other operators declare the right-hand side value as a
> {{Term.Raw}}, which can also be a bind marker.
> I think users will expect to be able to bind the argument this way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
