Hello all, We are having serious problems upgrading our app to Rails 3 because we have a custom gem in our app that is collection of ActiveRecord models. Rather than repeat myself, here is the link to the bug filed in lighthouse.
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/6157-activerecord-scope-class-method-requires-a-database-connection#ticket-6157-4 What I really need to know is if this really is a bug or if anyone know a workaround for this situation. Or, are we just stuck with it and should start to refactor our gem into a service or flip it to a different ORM like DataMapper? Our external gem is critical to our current application and this bug completely impedes a transition to Rails 3. Because this appears to be bug in the way gems and database configs are loaded I thought I should post it on the core-list. If this should be on dev list let me know and I will move it over. Thanks Peer -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en.
