Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I've found a couple of clues that this might be related to older library (ActiveRecord) or gem versions. For example, <a href="http://wrath.rubyonrails.org/pipermail/rails/2006-January/009470.html" rel="nofollow noreferrer">problems with fixtures even though rest of app seems okay</a> (after an upgrade) or <a href="http://dev.rubyonrails.org/browser/trunk/activerecord/lib/active_record/connection_adapters/abstract/connection_specification.rb?rev=7771" rel="nofollow noreferrer">this trac ticket</a>, which "stops gems from requiring an adapter from an old Active Record gem". Both of these are old, though, but it might be worth making sure your gems are up to date (if possible).</p> <p>Are you using the native rails MySQL adapter by any chance? This is now deprecated under rails, but it's conceivable it's still limping along.</p> <p>I've taken a very quick look at <code>connection_specification.rb</code>, too, which is where this error is coming from, and my best guess is that a reconnect is failing... but why (since it was obviously okay when you first started the app)? Are you doing something wild like calling <code>ActiveRecord::Base.establish_connection</code> in your application controller (or elsewhere)? </p> <p>Or perhaps something like: script runner is called from cron in the dead of night when the connection has dropped. Unfortunately, the runner is invoked with an incorrect <code>RAILS_ENV</code>. Thus the wrong stanza is read from <code>database.yml</code>, and that stanza contains an invalid <code>adapter:</code>?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload