On Oct 25, 1:08 am, Henrik N <[EMAIL PROTECTED]> wrote: > So basically, it seems that a thread in a controller action can run > after the action completes, but ActiveRecord can't. > > Is this an inherent limitation? Can I configure my way around it? I > was hoping 2.2 connection pools would mean this would work, but I > guess not.
Aha! Changing config.cache_classes = true to config.cache_classes = false in config/environments/development.rb fixed this. So I expect the class was reloaded, messing up the connection. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
