I''ve opened a ticket #7330 which resolves #5381 and #5382. The patch includes a unit test and the fix itself. I''d love to see this get rolled in at some point as it makes unit testing with multiple databases possible, which is something my team is dealing with and something others have to deal with as well if multiple databases are used from within an application. V/r Anthony Eden -- Cell: 808 782-5046 Current Location: Melbourne, FL --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On Jan 23, 2007, at 7:52 PM, Anthony Eden wrote:> I''d love to see this get rolled in at some point as it makes unit > testing with multiple databases possibleAh, this would be great. I ran into this trying to use a second database for testing with remote objects in a RESTFul application. Manfred --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---