- Original Message -
From: "Paul DuBois" <[EMAIL PROTECTED]>
To: "rory oconnor" <[EMAIL PROTECTED]>
Cc: "Rune Steinseth" <[EMAIL PROTECTED]>; "mysql list (choose midget)"
<[EMAIL PROTECTED]>
Sent: Tuesday, May 14, 2002 11
At 11:35 -0500 5/14/02, rory oconnor wrote:
>I'm having some trouble with this issue...I'm using perl DBI and mysql
>for a customer addressbook. I know MySQL won't needlessly update a row
>if nothing's changed, but since I'm using $rc = $sth->rows; as an
>indicator of success, customers will get
I'm having some trouble with this issue...I'm using perl DBI and mysql
for a customer addressbook. I know MySQL won't needlessly update a row
if nothing's changed, but since I'm using $rc = $sth->rows; as an
indicator of success, customers will get stuck if they decide they don't
want to change a
At 10:41 +0100 3/14/02, Rune Steinseth wrote:
>Hi all,
>I have changed database for my Java app to MySQL. The
>app was developed with SQL Server. Some of the logic
>is dependent on getting the no. of rows updated
>returned after an UPDATE query. MySQL does only
>return the rows that are really
Hi all,
I have changed database for my Java app to MySQL. The
app was developed with SQL Server. Some of the logic
is dependent on getting the no. of rows updated
returned after an UPDATE query. MySQL does only
return the rows that are really updated, not the rows
matched of an UPDATE. This ca
