Is Rails 3 integrated with Sequel?

Question

At least four github repositories that claim to contact Sequel with the latest beta version of Rails 3.

Has anyone successfully replaced ActiveRecord with Sequel in a Rails 3 project? Could you give some tips on how best to do this?

I am interested in starting a new project on Rails 3 and trying to get on the right foot: the perfect sequel, minitest and omniauth (with development if this is not painful). I know this is not a blessed stack, but these gems appeal to my common sense. I am looking for any advice that will help me deal with any problems and conflicts.

Answer 1

I used Sequel with Rails 2 and 3. If you do not use any ActiveRecord integration features, it is really easy even with Rails 2, you just need to configure the Sequel database connection manually or in the environment file (environment.rb or environment / *. rb) or in the initializer. Sequel models are still in the / models / application.

With Rails 3 and the active_model Sequel plugin, integration should work fine in terms of code. Most of what github repositories do is deal with tasks such as rakes and generators, which, while nice, are not really needed.

Answer 2

Since sequel rails are no longer supported, I was looking for forks. The TalentBox version seems promising and actively supported.

I must add, however, the migrations ( rake db:migrate , etc.) seem to be somewhat broken. There are several patches in my fork, see Section iblue / continued-rails . I eventually pushed them to talentbox when they are stable.

EDIT: TalentBox now works fine.