[
https://issues.apache.org/jira/browse/CASSANDRA-4890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488676#comment-13488676
]
Jonathan Ellis commented on CASSANDRA-4890:
-------------------------------------------
+1
> Don't allow prepared marker inside collections
> ----------------------------------------------
>
> Key: CASSANDRA-4890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4890
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0 beta 1
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.2.0 beta 2
>
> Attachments: 4890.txt
>
>
> Currently the parser don't disallow preparing queries like (where l is a
> list<string>):
> {noformat}
> INSERT INTO test (k, l) VALUES (0, [1, ?, 2])
> {noformat}
> However, we don't handler it correctly. And in fact we can't really handle it
> properly currently since we return the name of the prepared column during
> prepare and here the marker don't correspond to a column (concretely, the
> code currently return l and list<string> for the name and type of the
> prepared value, which is incorrect). We also don't handle it during execute,
> though that last could in theory be fixed with some effort.
> But overall I don't think allowing that kind of things is really useful (you
> can of course prepare the whole collection), so I suggest just refusing it
> for now.
--
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
