cherring / connection_ninja Goto Github PK

I did the following test. A have a Application model that points to a DB using use_connection_ninja.
Them, on console I did the following:

Application.connection
Application.all
ActiveRecord::Base.connection
Application.all

On the last command I received: "Mysql::Error: MySQL server has gone away".
So, seems that I cant use the default application database. Only those using use_connection_ninja.
Is that true?

Is there a way to use the existing db: rake tasks on the alternative connection database?
I want to have a separate test version of the external database, locally, and load fixture data into it (machinst), although my app treats it as read-only.
Suggestions? for now i just created it manually and wrote a separate rake task to seed it.

I'm not a Rails 3 user yet so I'm not sure if this is a Rails 3 issue, but grouping doesn't work in the older Rails 2.X version....I had to dig through the old config files to see how it works. You might want to point that out on the main connection_ninja page so other users don't spend as much time as I did trying to figure out why my second connection wont connect to the right db.

specifically I'm talking about database_development, database_production, etc.... VS database: development: production: etc...