I'm using Sequel with a Rails 3.2.8 application and have had zero issues so far. I'm not using sequel-rails so your mileage my vary.
I had to remove the require 'rails/all' from the config/application.rb and instead require in specific features of Rails. There was a bunch of ActiveRecord configuration that needed to be commented out as well. There are a few different ways you can connect to your database, but I found that creating an initializer was the cleanest solution. Thanks, Doug Tykocki On Fri, Nov 23, 2012 at 10:38 AM, Jason Rogers <[email protected]> wrote: > Is anyone using Sequel in a Rails 3.2.x app? I would like to use it on our > new project, and just want to hear any gotchas. (I had proposed not using > the Rails stack but was voted down on that.) > > I plan on using the TalentBox gem ( > https://github.com/TalentBox/sequel-rails). I know that using a gem like > this is not necessary, but I feel that any lack of feature parity with AR > will make my sell very difficult. > > Thanks. > > -- > Jason Rogers > > -- > You received this message because you are subscribed to the Google Groups > "sequel-talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sequel-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
