# RDBI 0.9.0 (release candidate) is out for testing

**URL:** <https://www.ruby-forum.com/t/rdbi-0-9-0-release-candidate-is-out-for-testing/193680>\
**Category:** Ruby\
**Created:** [August 22, 2010, 4:27am UTC](https://www.ruby-forum.com/t/rdbi-0-9-0-release-candidate-is-out-for-testing/193680 "2010-08-22T04:27:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![happolati](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/51bf81/32.png) [@happolati](https://www.ruby-forum.com/u/happolati)\
**Post date:** [August 22, 2010, 4:27am UTC](https://www.ruby-forum.com/t/rdbi-0-9-0-release-candidate-is-out-for-testing/193680/1 "2010-08-22T04:27:41Z")

</div>

RDBI is yet-another database access library, currently in release  
candidate. It aims to provide a consistent interface to many lower  
level databases. At least initially, it intends to provide a  
compelling replacement to Ruby/DBI, of which current maintainers are  
fed up with. 🙂

[http://rdbi.hollensbe.org](http://rdbi.hollensbe.org) for documentation and more information about  
the library.

This release candidate is released as 0.9.0 and patch levels will be  
incremented as we approach 1.0, which will be the final initial  
release of RDBI.

RDBI is released as several parts as gems on [rubygems.org](http://rubygems.org):

```
* methlab is a method toolkit library.
* typelib is a filter chaining system intended to assist with type
  conversion.
* epoxy is a database agnostic binding layer.
* rdbi is the core component.
* rdbi-dbrc is a configuration layer.
* rdbi-driver-postgresql is a PostgreSQL driver.
* rdbi-driver-mysql is a MySQL driver.
* rdbi-driver-sqlite3 is a SQLite3 driver.
* rdbi-result-driver-json is a result driver (see docs) that
  yields json directly from results. YAML, Struct, and Array
  result drivers come included with RDBI's core.

```

Please feel free to reply to this message with any questions or  
concerns.

Thanks,

Erik H. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)
