[
https://issues.apache.org/jira/browse/CASSANDRA-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482165#comment-13482165
]
Sylvain Lebresne commented on CASSANDRA-3799:
---------------------------------------------
bq. It seems like the entire statement could be processed server side
I'm not a fan because I think this kind of type conversion is mostly (to not
say only) useful with cqlsh.
Now I think this could be fixed in a slightly different way by adding support
for prepared statements in cqlsh (though maybe it's already supported, I
haven't really looked). If we do, you could have something like:
{noformat}
cqlsh> PREPARE INSERT INTO TABLE (name, column, value) VALUES (?, ?, ?);
=> prepared statement 0
cqlsh> EXECUTE 0 WITH name = bytes('yo), column = bytes('donthis'), value =
bytes('onserver')
{noformat}
The syntax is just an example but the point is that now the EXECUTE itself is
not a CQL statement but rather a cqlsh command, and so supporting type
conversion functions is trivial.
Granted this is slightly more verbose that with the CLI, but doesn't seem to me
like it's a big deal, and I think you really only need that when you work with
blobs.
> cqlsh: ASSUME should also change how values are sent to cassandra
> -----------------------------------------------------------------
>
> Key: CASSANDRA-3799
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3799
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Affects Versions: 1.0.3
> Reporter: paul cannon
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Labels: cqlsh
> Fix For: 1.3
>
>
> cqlsh's ASSUME command currently only changes how query *return* values are
> deserialized, and never transforms user CQL text before sending to Cassandra.
> Apparently cassandra-cli also changes how values are interpreted and
> marshaled for Cassandra, so user expectation is that cqlsh should also do
> this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
