[
https://issues.apache.org/jira/browse/CASSANDRA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002253#comment-13002253
]
Gary Dusbabek commented on CASSANDRA-2124:
------------------------------------------
bq. For this, either we need to introduce a wrapper or Ascii, BytesType, UUID
etc. classes need to provide a way for toString() calls.
for AsciiType use getString(), for BytesType use getBytes(), for UUID use
getObject and cast to a java.util.UUID.
I think this patch set is ready to commit and we can move on to the next
iteration (ResultSetMetadata or whatever).
> JDBC driver for CQL
> -------------------
>
> Key: CASSANDRA-2124
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2124
> Project: Cassandra
> Issue Type: New Feature
> Components: API
> Reporter: Eric Evans
> Assignee: Vivek Mishra
> Priority: Minor
> Labels: cql
> Attachments: Cassandra-2124_v1.0, Cassandra_2124_decoder.patch,
> cassandra-0.7.1-2124_v2.0, cassandra-0.7.1-2124_v2.1,
> cassandra_generic_decoder.patch, cassandra_generic_decoder_v1.1.patch,
> v1-0001-first-pass-at-column-decoding.txt,
> v1-0002-clean-up-JdbcDriverTest.txt,
> v1-0003-implements-getXXX-methods-to-return-values-of-the-corr.txt,
> v1-0004-more-comments-in-ColumnDecoder.txt
>
>
> A simple connection class and corresponding pool was created for CQL as a
> part of CASSANDRA-1710, but a JDBC driver (either in addition to, or as a
> replacement for) would also be interesting.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
