I am going to start a project from scratch with MySQL. Is it a good idea to go ahead with MySQL 5? Is there any gotcha with that version as of today? -- fxn "We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise." -- Larry Wall in comp.lang.perl
on 2005-12-22 11:26
on 2005-12-22 11:53
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. Warren Seltzer
on 2005-12-22 12:11
On 12/22/05, Warren Seltzer <email@example.com> wrote: > > 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. Why?
on 2005-12-22 14:32
On 12/22/05, Rodrigo Alvarez Fernández <firstname.lastname@example.org> wrote: > > Why? > > 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.