cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2475) Prepared statements
Date Mon, 16 May 2011 21:12:47 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034315#comment-13034315
] 

Jonathan Ellis commented on CASSANDRA-2475:
-------------------------------------------

Traditionally, a prepared statement API would look something like this:

{noformat}
  int prepare_cql_query(1:binary query, 2:Compression compression);
  void execute_prepared_query(1:int query_handle, 2:list<binary> parameters, 3:Compression
compression);
{noformat}

... that is, prepare would parse and plan the query, then execute would supply the parameters
to be bound to query variables.

On the client side, the APIs are well-defined, e.g. JDBC's prepareStatement. (Note that we
currently "fake" these APIs on top of the standard execute_cql_query.)

> 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

Mime
View raw message