[ https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13275917#comment-13275917 ]
Jonathan Ellis commented on CASSANDRA-4242: ------------------------------------------- bq. I do not see how we can feed parameters from a map (unordered) to a list of values But why would we need to? I thought the goal here is introspection of what a prepared statement returns. Executing the statement works fine. bq. can't find CqlResult.column_types in trunk Because that's a change I'm proposing. :) bq. I would prefer a binary type for column names instead of string. 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. > 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 > > > 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