[
https://issues.apache.org/jira/browse/CASSANDRA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054170#comment-13054170
]
Rick Shaw commented on CASSANDRA-2475:
--------------------------------------
I think prepared statements for Cassandra is a nice convenience that seems very
natural, but it is born out of the way relational systems work (pre-compiling,
strategies and the like). I just don't see a lot of performance advantage is
going to be gained in Cassandra over the "faked" way it is done now.
The other question I have is about the above code snippet. It implies (i
think?) that the caller passes in CQL and get a handle to a "something" that is
going to be stored on the Server side? That seems to be fraught with problems?
How long does it live? How does the server side know when you might be done
with it? I wonder if the complication of keeping state on the server side and
substituting binary values into a new tokenized structure will really be faster
than parsing the string again with ANTLR?
> Prepared statements
> -------------------
>
> Key: CASSANDRA-2475
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2475
> Project: Cassandra
> Issue Type: Sub-task
> Components: API, Core
> Reporter: Eric Evans
> Labels: cql
> Fix For: 1.0
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
