Jason Fox

Recently I had a problem with Bj where it would not start up.  Nothing was written to the backgroundjob log or Rails log and no exception was being thrown.  To make the problem even stranger, Bj would start-up just fine in development but not in production but worked just fine in production from script/console.  After digging into the Bj code and adding some debug statements I found the problem.

# database.yml
development:
  adapter: mysql
  database: my_development
  username: me
  password: password
  host: localhost
  port: 3306

test:
  adapter: mysql
  database: my_test
  username: me
  password: password
  host: localhost
  port: 3306

production:
  development

Bj was getting an ActiveRecord::ConnectionNotEstablished exception but was swallowing it.  The solution was to explicitly define the production database connection in database.yml.

I recently found the need to provide UUIDs for ActiveRecord models in a service that I’m developing.  I wasn’t able to find a suitable soution, so, I rolled my own.  Enter acts_as_universally_unique.  The plugin simply adds a (customizabe) UUID field to all ActiveRecord models that act_as_universally_unique.  I will be adding additional methods (and test cases) to it shortly.