I''m getting a weird MySQL error with Rails on bidwell.textdrive.com: SQL-query: UPDATE models SET `picture` = ''1'' , `last` = NULL , `info` = '''' , `art` = ''71567'' , `sizes` = ''35-43'' , `thumb` = ''1'' WHERE id =57 MySQL said: #1030 - Got error -1 from storage engine The same app (and same query) works fine on my own box. This is a normal table update done by ActiveRecord. I''ve tracked the problem down to the row where info is been set to an empty string. There shouldn''t be any problem with that AFAIK, it''s not a required field and Rails interprets empty text fields as empty strings (as opposed to nil). Has anyone any experience with this kind of situation? I think the difference between my box and the server is that I''m running MySQL 4.0.x and the server 4.1.x. However, I don''t understand why 4.1 wouldn''t accept empty strings, so I guess this is a bug in MySQL. //jarkko -- Jarkko Laine http://jlaine.net http://odesign.fi _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On Apr 6, 2005 11:40 AM, Jarkko Laine <jarkko-k1O+Gnc6WpmsTnJN9+BGXg@public.gmane.org> wrote:> I''m getting a weird MySQL error with Rails on bidwell.textdrive.com: > > SQL-query: > > UPDATE models SET `picture` = ''1'' , > `last` = NULL , > `info` = '''' , > `art` = ''71567'' , > `sizes` = ''35-43'' , > `thumb` = ''1'' WHERE id =57 > > MySQL said: > > > #1030 - Got error -1 from storage engine > > The same app (and same query) works fine on my own box. This is a > normal table update done by ActiveRecord. > > I''ve tracked the problem down to the row where info is been set to an > empty string. There shouldn''t be any problem with that AFAIK, it''s not > a required field and Rails interprets empty text fields as empty > strings (as opposed to nil). > > Has anyone any experience with this kind of situation? I think the > difference between my box and the server is that I''m running MySQL > 4.0.x and the server 4.1.x. However, I don''t understand why 4.1 > wouldn''t accept empty strings, so I guess this is a bug in MySQL. > > //jarkko > > -- > Jarkko Laine > http://jlaine.net > http://odesign.fi > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > > >I experienced the same issue. IIRC, someone mentioned that this had to do with InnoDB tables; try changing your tables to MyISAM instead. Dave -- Dave Goodlad dgoodlad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org or dave-eHfbeeWWzZOw5LPnMra/2Q@public.gmane.org http://david.goodlad.ca/
On 6.4.2005, at 20:50, David Goodlad wrote:> > I experienced the same issue. IIRC, someone mentioned that this had > to do with InnoDB tables; try changing your tables to MyISAM instead.Thanks, but unfortunately MyISAM tables don''t support transactions. I''ll try to drop and recreate the database. If that doesn''t help, I think I''ll change the db to PostgreSQL... //jarkko -- Jarkko Laine http://jlaine.net http://odesign.fi _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails