Archive for January 2010
If you’ve tried installing a plugin from github lately it seems everything’s not found..
As of Rails 2.3.5 there still is a open bug which is getting in the way of happy trails with ruby 1.9.x
Start up a shell with Ruby 1.8.x and install the plugin as usual. Then go back to working with Ruby 1.9.x. The fix will be out on rails 2.3.6 so a bit of patience and this will go away.
(Update) waiting for rails 2.3.6 .. seems rails 3 will be out before this is done
annoyingly enough , i had figured out the concept. Use DBI ODBC instead of DBD ADO… now ADO is going through some tug of war bullshit , which eventually will fade out when Microsoft gets its paws untangled
in the meanwhile , there towards the bottom is the answer
this is signigicant because the dbi gem in Ruby 1.9.1 is already on another version greater than the one desperately needed to make things work.
It should be noted that this version of the adapter was developed using both the ancient 0.0.23 version of DBI up to the current stable release of 0.4.1. Note that DBI 0.4.1 is the minimal for ruby 1.9 compatibility. Because later versions of DBI will be changing many things, IT IS HIGHLY NECESSARY that you max your install to version 0.4.1 which the examples below show. For the time being we are not supporting DBI versions higher than 0.4.1 this they settle down on new internal implementations.
Performance is seemingly OK
Rails has the built in ability to connect to multiple databases.
Short story is, you define databases through the database.yml file, beyond development, test and production. You can define sets of development, test and production databases that connect to any of the supported DB clients provided with Rails.
There are ruby adaptors for all major databases. There’s even ODBC support provided to finish opening up the ability for the DBs to connect.
Couple this with the ability for an AR object to define its own database connection. Add the ability to define an inherited class for an AR model.. Add the ability to set the table name, primary key names to each model.
Finish it up with the rails console.
a smart DBA can really milk this