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

Gary Dusbabek commented on CASSANDRA-2124:
------------------------------------------

bq. Should we replace rowmetadata with ResultsetMetaData?
The problem with using ResultSetMetaData is that it is a bad interface for 
Cassandra's sparse columns.  A good example is that column 0 in one row might 
map to a column named "foo", while column 0 in another row might map to a 
column named "bar".  The Wrappable interface exists so that JDBC driver 
implementations can provide features beyond the JDBC API without the ugliness 
of casting.  I think it is better to make the programmer fully aware that he is 
dealing with sparse columns and forcing him to use the RowMetaData API.

I'd like to hear your points on the benefits of using ResultSetMetaData though. 
 I admit that RowMetaData may not be the ideal way of accessing row-specific 
meta information.


> 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
>             Fix For: 0.8
>
>         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, 
> v3-0001-first-pass-at-column-decoding.txt, 
> v3-0002-clean-up-JdbcDriverTest.txt, 
> v3-0003-implements-getXXX-methods-to-return-values-of-the-corr.txt, 
> v3-0004-more-comments-in-ColumnDecoder.txt, 
> v3-0005-move-all-java-cql-into-jdbc-package-and-only-expose-.patch
>
>
> 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

Reply via email to