Ok, so it turned out he called mysql_affected_rows() after
commit, and that was the cause.
so it's solved...
however, would MySQL developers accept a feature request
asking for mysql_affected_rows() keeping the number of rows
across subsequent non-update, etc. queries?
At 21:21 8.1. 2001, Cynic wrote the following:
--------------------------------------------------------------
>There's a report in the PHP bug db
>(see http://bugs.php.net/bugs.php?id=7517) reporting that
>PHP function mysql_affected_rows(), which is only a wrapper
>to MySQL C API's mysql_affected_rows() always returns 0
>for queries on BDB tables.
>
>I'm an NT user, and can't check/reproduce this myself.
>Could someone please confirm/displace this? Reported version
>is 3.23.25.
>
>replies to cynic@stripped, please
>
>
>____________________________________________________________
>Cynic:
>
>A member of a group of ancient Greek philosophers who taught
>that virtue constitutes happiness and that self control is
>the essential part of virtue.
>
>cynic@stripped
>
>
>
>---------------------------------------------------------------------
>Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
>posting. To request this thread, e-mail win32-thread4727@stripped
>
>To unsubscribe, send a message to the address shown in the
>List-Unsubscribe header of this message. If you cannot see it,
>e-mail win32-unsubscribe@stripped instead.
------end of quote------
____________________________________________________________
Cynic:
A member of a group of ancient Greek philosophers who taught
that virtue constitutes happiness and that self control is
the essential part of virtue.
cynic@stripped
