On Tue, Mar 24, 2009 at 11:36 AM, Robert Walker <[email protected]> wrote: > I fully understand that other people's experience may vary, but from my > perspective switching to OpenBase solved a problem that MySQL just > wasn't able to handle. I'm not promoting OpenBase, and I've only used it > in production for this one special case. I use MySQL for most of my > applications and it typically works great.
In my opinion it was a mistake in making sqlite the default db for Rails. Any serious app will eventually have a test suite where you will need local test/development performance to be high. The sqlite db constantly being locked and unlocked only hurts performance. The modern CPU is moving towards more threads and more cores, meanwhile Rails development heads in the exact opposite direction. And look at the mail archives for all the beginners struggling to figure out how to get sqlite, and ruby-sqlite running on their systems, it's not like replacing mysql with sqlite gave them less to install or less issues overall. Seems to me they were trying to solve non-problems with the sqlite move. Any serious developer will already have a favorite db up and running, spec'd by his phb or otherwise, and I'd say it's never sqlite by default. I mean I understand why they did it, to try and bring in more new Rails users faster, more book sales, more everything. And to that I'd say why not ease the issues of the existing Rails users first, like how about some Oracle love for those of us working in research? Hmm? Just a thought. -- Greg Donald http://destiney.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 -~----------~----~----~----~------~----~------~--~---
