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
I''m using MySQL 5 for a couple of applications, one in production.
Haven''t had any problems with it.
-Jonny.
-----Original Message-----
From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
[mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On
Behalf Of Xavier Noria
Sent: Thursday, 22 December 2005 11:24 p.m.
To: rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
Subject: [Rails] advice on MySQL version
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
_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails
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 -----Original Message----- From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org [mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of Xavier Noria Sent: Thursday, December 22, 2005 12:24 PM To: rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org Subject: [Rails] advice on MySQL version 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
On 12/22/05, Warren Seltzer <warrens-uf+uqdaZT6qTt3WsUyM9gg@public.gmane.org> 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? _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On 12/22/05, Rodrigo Alvarez Fernández <papipo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > > On 12/22/05, Warren Seltzer <warrens-uf+uqdaZT6qTt3WsUyM9gg@public.gmane.org> 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? > >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.