On Fri, Feb 25, 2011 at 7:24 PM, Michael Granger <[email protected]> wrote: > Also, once you've used Sequel, it's extremely frustrating to try to use > AR for anything other than a simple objectstore.
I really like Sequel, we used it with Sinatra for our last project - we chose Sinatra + Sequel because Rails 2 required too many workarounds to deal with a legacy database and complex relationships that didn't fit the Rails pattern. Our current project we are putting a toe back into RoR - with Rails 3 ActiveRecord is *much* more flexible and more Sequel-like - really enjoying it - so if your statement above is about Rails 2.x and before I'd agree whole-heartedly - I'd disagree for Rails 3. One of our 'will it work' cases for RoR + AR was an A -> A_B_pivot_table -> B join case on a legacy database in read-only mode (since we don't own it) with Rails 3 AR - the code needed for the AR version was the same or less than what was needed for the Sequel implementation. Sequel is terrifc - AR is a lot more fun these days as well :). - Max -- 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.
