[
https://issues.apache.org/jira/browse/CASSANDRA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jon Hermes updated CASSANDRA-2500:
----------------------------------
Attachment: rbcql-0.0.0.tgz
v2.
Attaching rbcql ("CassDBD" in DBI parlance). No longer takes the `old JDBC`
approach of returning thrift objects, conforms to DBI return standards of array
of values and a matching array of column_info containing type info and column
names, the marshalling etc. is handled by DBI.
Now also correctly tracks schema changes by REing queries as they come in (what
pycql does). Should drop into a Rails system by including the package, changing
the DBI-URLs to prefix with "Cass", and making sure the input code is CQL, not
SQL.
Still not sure how best to require ruby c* bindings. (Looking at the
cassandra-rubygem, they include the bindings in a vendor dir and keep them up
to date.) Right now this expects interface/thrift/gen-rb/ to be in the same
directory.
2622 problem is fixed by including key_alias info in the internal metadata
(rubycql's copy of the schema).
> 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, 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
