ActiveRecord needs an adapter for every database you want work with and currently there are adapters for many non-commercial databases, but support for a lot of commercial ones is still missing.
It’s really not difficult to write an adapter and I will show you in detail, what you have to do to create an adapter for the famous foo database.
All path names below are relative to the rails/activerecord directory.
- Create a working environment
subversion and Rake have to be installed on your system. Detailed instructions for checking out Rails can be found under http://dev.rubyonrails.com.
- Find and install a Ruby driver for the foo database
Because DBI adds another layer of indirection, it will decrease performance and you should avoid using it for ActiveRecord. Please, do not misunderstand me: DBI is great but ActiveRecord needs as much performance as possible, so use a native driver instead.
- Create two test databases
The unit tests need two different databases. If the length of database names is not limited, call them _activerecord_unittest_ and _activerecord_unittest2_. Otherwise call them arunit and arunit2.
- Install the test databases
In directory test/fixtures/dbdefinitions_ create two files called foo.sql and foo2.sql containing the CREATE TABLE statements for the test databases. Copying and modifying existing files works best here.
Install the test databases using the SQL files. foo.sql is for database _activerecord_unittest_ (_arunit_) and foo2.sql is for _activerecord_unittest2_ (_arunit2_).
$ svn add test/fixtures/db_definitions/foo*.sql- Create test connections
Create a directory for the test connections:
$ svn mdkir test/connections/native_fooCreate test/connections/nativefoo/connection.rb_ by copying and modifying an existing one.
$ svn add test/connections/native_foo/connection.rb- Write the adapter
Implement the interface of class \AbstractAdapter, call your implementation \FooAdapter, and save it as lib/activerecord/connection_adapters/foo_adapter.rb_.
The source code of the existing adapters is full of inspiration and good ideas, so do not reinvent the wheel and use it, please.
If you need additional files put them into the
lib/activerecord/vendor_ directory.
$ svn add lib/active_record/connection_adapters/foo_adapter.rb
($ svn add lib/active_record/vendor/foo*)</pre>
- Load the adapter
Modify lib/activerecord.rb_ and add a require statement for the foo database adapter:
require 'active_record/connection_adapters/foo_adapter'- Run the unit tests
Add a new test task to Rakefile:
Rake::TestTask.new("test_foo") { |t|
t.libs << "test" << "test/connections/native_foo"
t.pattern = 'test/*_test.rb'
t.verbose = true
}
From the activerecord directory run:
$ rake test_fooFor more detailed instructions on running the unit tests see the file _RUNNING_UNIT_TESTS_.
- Fix bugs until all the tests run
If your database does not implement a feature that is required by some test cases but not by the \AbstractAdapter interface, you should document the failing tests somewhere.
- Modify install.rb
Add all files you’ve created to install.rb.
- Submit your changes
You can find instructions for this step on http://dev.rubyonrails.com.
category:Howto