Re: MySQL Stored Procedure works differently with DBI

On Feb 16, 2010, at 4:34 PM, Erik wrote:

> Solved. This seemes to have been an issue of "matched rows" vs. "changed rows". The use of stored procedures was not part of the scope of the problem. The different behaviors were the result of how different clients connect to the server.
> 
> This thread helped me understand the problem:
> http://lists.mysql.com/perl/72.
> 
> It seems that calling ROW_COUNT() when connected via DBD::mysql returns "matched rows" and not "changed rows"
> 
> I was not able to resolve this by adding "mysql_found_rows=0" to the DSN passed to DBD::mysql. It seemed to not have any effect.

It's mysql_client_found_rows, not mysql_found_rows.