Mysql 5 works fine with the new rails 1.0. Don’t hack around with older
versions of rails
unless you have some specific need to. Older versions of rails need
mysql-hackery to work
with mysql-5, but are tuned okay for mysql-4.0. Use the latest of both.
Actually, postgres is a better choice, but that’s up to you.
Mysql 5 works fine with the new rails 1.0. Don’t hack around with older
versions of rails
unless you have some specific need to. Older versions of rails need
mysql-hackery to work
with mysql-5, but are tuned okay for mysql-4.0. Use the latest of both.
Actually, postgres is a better choice, but that’s up to you.
It has a more complete feature set, and better adherance to ACID
behaviour in terms of not silently truncating, transforming, or
ignoring input rather than generating errors. If your application is
non-trivial, you will end up moving to PostgreSQL, or coding around
the shortcomings of MySQL.
But, I’m a zealot. Try Googling PostgreSQL vs MySQL and read what you
find. Now is the best time to decide, migration is doable, but not
always easy.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.