[
https://issues.apache.org/jira/browse/CASSANDRA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187875#comment-13187875
]
Rick Shaw commented on CASSANDRA-3634:
--------------------------------------
Perhaps it is a JDBC specific problem but often, tooling will use {{setInt()}}
if it is a number to be stored in a string column and more frequently a
{{setString()}} for an integer field. The concern is the {{PreparedStatement}}
suite of methods provides a lot of flexibility to do these kinds of implied
transformations that will be difficult without cooperation between the client
and server. to do on the client side only, will require knowing the entire
potential schema cached on the client side.
> compare string vs. binary prepared statement parameters
> -------------------------------------------------------
>
> Key: CASSANDRA-3634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3634
> Project: Cassandra
> Issue Type: Sub-task
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Eric Evans
> Priority: Minor
> Labels: cql
> Fix For: 1.1
>
>
> Perform benchmarks to compare the performance of string and pre-serialized
> binary parameters to prepared statements.
--
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
