in reply to SOLVED: DBI SQL Returns Less than Direct SQL

Your use of $sth->rows() is buggy, and might be confusing the issue. From the DBI docs:

For SELECT statements, it is generally not possible to know how many rows will be returned except by fetching them all. Some drivers will return the number of rows the application has fetched so far, but others may return -1 until all rows have been fetched. So use of the rows method or $DBI::rows with SELECT statements is not recommended.

Replies are listed 'Best First'.
Re^2: DBI SQL Returns Less than Direct SQL
by DaveNagy (Initiate) on Oct 18, 2011 at 15:33 UTC

    True! But, this count matches the rows returned in results arrays, whether as the result of an EXECUTE or other method.

    The documentation cautions that getting a count of rows might not work for certain drivers but doesn't explicitly say that for MySQL the results are not guaranteed. I had this code after the loop where I processed the results and the row count matches the number of rows returned in arrays (and for other search words, I do get more than 1 row but always less than shown in pure SQL via PHPAdmin and other query processes.)

    Thanks, Dave
[reply]

In Section Seekers of Perl Wisdom