Markus**: ***AH! Für die Nachwelt! Ich weiß was los ist! ***

Beitrag lesen

Erstmal einen Dank an Euch auf für die Hilfe!

Ich fand folgenden Eintrag in einer Newsgroup, der die Problematik und eine Lösung schildert. Es ist ein konfigurations-problem!
-----------------------------------------

Hmmm, I forgot about this outstanding issue. This is a known behaviour
of the MySQL engine, call it a bug or a feature, as you like. (It declares
"affected" as "changed".) The behaviour you are expecting can be enabled
by setting the C flag CLIENT_FOUND_ROWS when connecting to the database.

I have now uploaded a version 1.2205 of the Msql-Mysql-modules to CPAN
which has the following new feature: When connecting with

DBI->connect("DBI:mysql:test;mysql_client_found_rows=0", ...)

then you have the old behaviour. With

DBI->connect("DBI:mysql:test;mysql_client_found_rows=1", ...)

you have CLIENT_FOUND_ROWS set, thus your query will always return 1.

The default is 0, however you can change this by compiling the
Msql-Mysql-modules with

perl Makefile.PL --config --mysql-use-client-found-rows

in which case the default is 1.

Monty, I dislike that this must be choosen while connecting to the
client. Couldn't we make this part of the MYSQL structure?

-----------------------------------------
Quelle: http://lists.mysql.com/perl/250?f=plain

Gruß, Markus