[EMAIL PROTECTED] wrote: > What might happen in multithreaded mode?? Any dynamic change to the conditions of an association would be common to all Rails handlers associated with that process. Prior to Rails 2.2, this is was always one, so there was no problem. But if you use Rails in multi-threaded mode, one thread could change the conditions used by another thread before those conditions are built into a DB query.
So you'd either have to put an exclusive lock around that query (which may have a significant impact on the database parallelism), or rewrite the AR code to fork a thread-private condition whenever one is dynamically set. -- Rails Wheels - Find Plugins, List & Sell Plugins - http://railswheels.com --~--~---------~--~----~------------~-------~--~----~ 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 [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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
