[ https://issues.apache.org/jira/browse/CASSANDRA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185078#comment-13185078 ]
Jonathan Ellis edited comment on CASSANDRA-3634 at 1/12/12 5:18 PM: -------------------------------------------------------------------- That's not what I meant. Suppose I have a custom geohash type. In a String-based PS world, I need to provide a geohash.toString method for each client driver. In a binary-based PS world, I need to provide a geohash.toByteBuffer method. So either way you're going to have to write custom code per client driver. Update: this comment was obsoleted before I posted it by concurrent editing. It sounds like we are in violent agreement. was (Author: jbellis): That's not what I meant. Suppose I have a custom geohash type. In a String-based PS world, I need to provide a geohash.toString method for each client driver. In a binary-based PS world, I need to provide a geohash.toByteBuffer method. So either way you're going to have to write custom code per client driver. Update: this comment was obsoleted before I posted it by concurrent editing. :) > 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