[ https://issues.apache.org/jira/browse/CASSANDRA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044069#comment-13044069
]
Jonathan Ellis commented on CASSANDRA-2500:
-------------------------------------------
The point of having different modules is to make it clear what each is supposed to do. To
a novice, mixing the old gem API into a CQL driver would be extremely confusing.
The main goal of having them in-tree is to (1) make clear what the "official" client is for
a given language and (2) by so doing prevent the proliferation that is causing so much confusion
with the old Thrift api. (See: http://stackoverflow.com/questions/6157760/rails-orm-for-cassandra)
> 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
> Reporter: Jon Hermes
> Assignee: Jon Hermes
> Attachments: 2500.txt, genthriftrb.txt
>
>
> 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