Not sure but 2 issue when upgrading to AR 1.5 with Rails .94 1. When running on MySQL 4.1.x it you need to make sure that passwords use the new format of passwords not the old 4.0.7< format. The unfortunate side effect of this is that CocoaMySQL only uses the old format. Not a big deal just something I saw since we are using a fairly old data set. 2. find_by_sql SELECT statements such as "SELECT table1.id, table1.subject, table2.id AS rid FROM table1, table2 WHERE... no longer returned objects that contain "rid" -- Lon Baker
Hmm just upgraded rails and my application immediately stopped working. turns out that the database connection was rejected by mysql, because the mysql root account was using an empty password (i assume). After creating another db user (with password) my app is working fine now. Is this a related bug too? On Mon, 17 Jan 2005 20:14:23 -0500, Lon Baker <lon-JCsVN+o+Xp98UrSeD/g0lQ@public.gmane.org> wrote:> Not sure but 2 issue when upgrading to AR 1.5 with Rails .94 > > 1. When running on MySQL 4.1.x it you need to make sure that passwords > use the new format of passwords not the old 4.0.7< format. The > unfortunate side effect of this is that CocoaMySQL only uses the old > format. Not a big deal just something I saw since we are using a fairly > old data set. > > 2. find_by_sql SELECT statements such as "SELECT table1.id, > table1.subject, table2.id AS rid FROM table1, table2 WHERE... no longer > returned objects that contain "rid" > > -- > Lon Baker > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
This is a bug. I have fixed in this patch that David has already incorporated: http://dev.rubyonrails.org/changeset/454 -Pelle On Tue, 18 Jan 2005 17:24:39 +0800, boonhoo <theebh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hmm just upgraded rails and my application immediately stopped > working. turns out that the database connection was rejected by mysql, > because the mysql root account was using an empty password (i assume). > > After creating another db user (with password) my app is working fine > now. Is this a related bug too? > > > On Mon, 17 Jan 2005 20:14:23 -0500, Lon Baker <lon-JCsVN+o+Xp98UrSeD/g0lQ@public.gmane.org> wrote: > > Not sure but 2 issue when upgrading to AR 1.5 with Rails .94 > > > > 1. When running on MySQL 4.1.x it you need to make sure that passwords > > use the new format of passwords not the old 4.0.7< format. The > > unfortunate side effect of this is that CocoaMySQL only uses the old > > format. Not a big deal just something I saw since we are using a fairly > > old data set. > > > > 2. find_by_sql SELECT statements such as "SELECT table1.id, > > table1.subject, table2.id AS rid FROM table1, table2 WHERE... no longer > > returned objects that contain "rid" > > > > -- > > Lon Baker > > > > _______________________________________________ > > Rails mailing list > > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- http://talk.org + Live and direct from Panama http://SoapBX.com + Get on the box and shout
> 1. When running on MySQL 4.1.x it you need to make sure that passwords > use the new format of passwords not the old 4.0.7< format. The > unfortunate side effect of this is that CocoaMySQL only uses the old > format. Not a big deal just something I saw since we are using a > fairly old data set.A version of CocoaMySQL using the new passwords format is available here: http://www.theonline.org/cocoamysql/ -[s]