cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Chalamet (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
Date Tue, 15 May 2012 18:09:17 GMT


Pierre Chalamet commented on CASSANDRA-4242:

But why would we need to? I thought the goal here is introspection of what a prepared statement
returns. Executing the statement works fine.
I thought the cinematic was:
1/ prepare_cql_query
2/ execute_prepared_cql_query using parameters as specified by 1/

I just do not want to know the name of the parameters in CqlPreparedResult, I need this to
*bind* parameters from various data source (which expose unordered named values).
The order of values is then really important from pov of the execution of query.

Am I missing something so ?

Column names are always strings in CQL3. See
for a quick summary and CASSANDRA-2474 for the gory details.
Sorry, I should have read the spec first :-) But OK but I insist to have binary values - it
is more efficient that hex encoded strings.
> Name of parameters should be available in CqlPreparedResult
> -----------------------------------------------------------
>                 Key: CASSANDRA-4242
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Pierre Chalamet
>            Priority: Minor
>         Attachments: 4242.txt
> Client side, it could be nice to have the name of parameters in CqlPreparedResult. This
could allow parameters mapping by name instead of by index.
> {code}
> struct CqlNameType {
>     1: required binary key,
> 	2: required string type
> }
> struct CqlPreparedResult {
>     1: required i32 itemId,
>     2: required i32 count,
>     3: optional list<string> variable_types,
>     4: optional list<CqlNameType> name_types
> }
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message