cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2475) Prepared statements
Date Tue, 17 May 2011 04:00:47 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034535#comment-13034535
] 

Eric Evans commented on CASSANDRA-2475:
---------------------------------------

bq. The thinking being that it's easier for a client to encode as string?

Well, the thinking being that the code to do so already exists.  It's also pushing some logic
back to the client and opening up the possibility for a whole class of bugs (multiplied by
the number of clients that have to implement it).

This isn't entirely hypothetical, it was recently discovered that Pycassa treated IntegerType
as always being 4 bytes in length, and that had gone undiscovered for a long time.  The string
representation of a number though, can be parsed by IntegerType.fromString() node-side consistently
regardless of the client. 

> Prepared statements
> -------------------
>
>                 Key: CASSANDRA-2475
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2475
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API, Core
>            Reporter: Eric Evans
>              Labels: cql
>             Fix For: 1.0
>
>


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message