10 messages in com.mysql.lists.perlmSQL: Number of rows affected never c...
FromSent OnAttachments
Paul Hoepfner-Homme03 Mar 2001 09:00 
Jochen Wiedmann03 Mar 2001 11:33 
Paul Hoepfner-Homme05 Mar 2001 07:08 
Jochen Wiedmann05 Mar 2001 08:39 
Paul Hoepfner-Homme05 Mar 2001 09:13.pl
Jochen Wiedmann06 Mar 2001 03:37 
Paul Hoepfner-Homme06 Mar 2001 08:44 
Paul Hoepfner-Homme06 Mar 2001 09:00 
Dodger06 Mar 2001 11:27 
Paul Hoepfner-Homme07 Mar 2001 09:07 
Subject:mSQL: Number of rows affected never correctly returned
From:Paul Hoepfner-Homme (pmho@student.math.uwaterloo.ca)
Date:03/03/2001 09:00:42 AM
List:com.mysql.lists.perl

Hello,

I've got an mSQL 2.0.11 server installed and properly set up with Perl with the mSQL modules. But every time I run any query on my mSQL database with the Perl mSQL modules and try to determine the number of rows affected by the query, $sth->rows() invariably returns -1, regardless of whether it was a SELECT, UPDATE or INSERT query. I went into the mSQL console myself and tried the exact same queries and it always reported the correct number of rows affected, not -1 as the Perl mSQL module does.

I am moving over to mSQL from a tiny CSV database (I was using the Perl DBD/CSV modules). With my CSV database I always got the correct number of rows affected by calling $sth->rows(). I am now using the identical code I used with the CSV database with the mSQL module, so I don't think there's anything wrong with my code, seeing as it worked perfectly using the standard DBI calls with a different database system.

Is this a bug in the mSQL module?

Thanks for your help, Paul