> I wasn't aware of that particular setting, but it does not appear to work > under Rails 1.1.6, at any rate. I added it to both environment.rb and > environments/production.rb, and it seemed to have no effect. Am I doing > something wrong? > > As far as I can tell, it seems that the database initialization happens > early enough in the process that we can't add to the list of adapters before > it blows up.
Yeah, I can't see how that'd work at all ;), seems no one's tried to use it before ;). David added it, the ticket's available here: http://dev.rubyonrails.org/ticket/1958 So it seems that setting it in environment rb before the initializer runs lets you override that behaviour. The config. option doesn't seem to work at all. Perhaps david or stefan could chime in? -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---