[ https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276071#comment-13276071 ]
Pierre Chalamet edited comment on CASSANDRA-4242 at 5/15/12 6:24 PM: --------------------------------------------------------------------- {quote} But why would we need to? I thought the goal here is introspection of what a prepared statement returns. Executing the statement works fine. {quote} 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 ? {quote} Column names are always strings in CQL3. See http://www.datastax.com/dev/blog/schema-in-cassandra-1-1 for a quick summary and CASSANDRA-2474 for the gory details. {quote} Sorry, I should have read the spec first :-) was (Author: pchalamet): {quote} But why would we need to? I thought the goal here is introspection of what a prepared statement returns. Executing the statement works fine. {quote} 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 ? {quote} Column names are always strings in CQL3. See http://www.datastax.com/dev/blog/schema-in-cassandra-1-1 for a quick summary and CASSANDRA-2474 for the gory details. {quote} 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: https://issues.apache.org/jira/browse/CASSANDRA-4242 > Project: Cassandra > Issue Type: Improvement > Components: Core > Affects Versions: 1.1.0 > Reporter: Pierre Chalamet > Priority: Minor > Attachments: 4242.txt, 4242_2.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira