Greg Donald wrote: > On Wed, Oct 7, 2009 at 5:50 AM, Marnen Laibow-Koser > <[email protected]> wrote: >> Anyway, mySQL and SQLite are problematic > > I've used both much success over the years. What sort of problems are > you having?
This is my main reason against MySQL: PostgreSQL has a transactional DDL so when a Rails migration breaks the database undoes all the changes it made. MySQL leaves the database half-changed and maybe in an inconsistent state. That's awful when it happens in production, maybe in a migration that was moving data around after having removed and added columns. It's not always possible to test everything in pre-preproduction so PostgreSQL is a much safer than choice MySQL. Granted, it's probably possible to code around this limitation of MySQL but it costs more than just using a (IMHO) better db. Paolo -- 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 [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 -~----------~----~----~----~------~----~------~--~---
