It has to do with multiple connections to one database. It has, however, always been possible to have some models living in one database, and others living in others, if that's what you want. Relationships accross databases don't always work perfectly, if you're trying to do fancy things. (Like, pre-loading a relationship accross databases).
For using multiple databases in your app, see: http://wiki.rubyonrails.org/rails/pages/HowtoUseMultipleDatabases Incidentally, even pre Rails 2.2, I have had success using multiple connections to a single db in different threads, using the mysql gem adapter. Now I wonder if the mysql gem adapter is actually non-blocking though, or if my different threads were still blocking on db access. Jonathan boblu wrote: > Can anybody tell me about this? > Does this "connection pool" have something to do with multiple > database connection? > Or it is only for concurrent access with one database? -- Posted via http://www.ruby-forum.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 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 -~----------~----~----~----~------~----~------~--~---
