[
https://issues.apache.org/jira/browse/CASSANDRA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079333#comment-13079333
]
Kelley Reynolds commented on CASSANDRA-2500:
--------------------------------------------
Upon further investigation, I think that writing a straight DBI driver as the
premier ruby CQL implementation is a bad idea. The largest problem comes from a
mismatch in the assumptions the DBI code makes that does not hold true with one
of Cassandra's most powerful features, column slicing. DBI assumes that the
column metadata does not change with each row but with Cassandra it does with
some frequency. Altering DBI to not make those assumptions is non-trivial and
it's unlikely they'd be accepted back into the tree anyway. I think at this
point the best course of action is to write something that behaves just like
DBI but doesn't use that framework at all to get the full capability of CQL and
then for a DBI driver, use that thing but disallow slicing or any other
operations that break fundamental DBI assumptions.
> Ruby dbi client (for CQL) that conforms to AR:ConnectionAdapter
> ---------------------------------------------------------------
>
> Key: CASSANDRA-2500
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2500
> Project: Cassandra
> Issue Type: Task
> Components: API
> Reporter: Jon Hermes
> Assignee: Pavel Yaskevich
> Labels: cql
> Fix For: 0.8.4
>
> Attachments: 2500.txt, genthriftrb.txt, rbcql-0.0.0.tgz
>
>
> Create a ruby driver for CQL.
> Lacking something standard (such as py-dbapi), going with something common
> instead -- RoR ActiveRecord Connection Adapter
> (http://api.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/AbstractAdapter.html).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
