You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Christoph Hack (JIRA)" <ji...@apache.org> on 2012/08/27 23:29:11 UTC

[jira] [Updated] (CASSANDRA-4577) Allow preparing queries without parameters

     [ https://issues.apache.org/jira/browse/CASSANDRA-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christoph Hack updated CASSANDRA-4577:
--------------------------------------

    Description: 
Currently it's not possible to prepare any queries that do not take any parameters using Cassandra's new native protocol because of an assertion error.

This makes client development rather difficult (you need to parse CQL queries to detect the number of parameters and skip the preparation of those) and there is probably no reason to handle queries with no parameters separately.

  was:
Currently it's not possible to prepare any queries that do not take any parameters using Cassandra's new native protocol because of an assertion error.

This makes client development rather difficult (you need to parse CQL queries to detect the number of parameters and skip the preparation of those) and there is probably no reason thread queries with no parameters separately.

    
> Allow preparing queries without parameters
> ------------------------------------------
>
>                 Key: CASSANDRA-4577
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4577
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Christoph Hack
>         Attachments: trunk-4577.txt
>
>
> Currently it's not possible to prepare any queries that do not take any parameters using Cassandra's new native protocol because of an assertion error.
> This makes client development rather difficult (you need to parse CQL queries to detect the number of parameters and skip the preparation of those) and there is probably no reason to handle queries with no parameters separately.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira