12 messages in com.mysql.lists.perlRe: Drivers giving different results
FromSent OnAttachments
Jochen Wiedmann25 May 1999 11:10 
Vivek Khera25 May 1999 12:01 
Jochen Wiedmann25 May 1999 13:18 
Tim Bunce25 May 1999 15:10 
Dan Busarow28 May 1999 14:25 
Jochen Wiedmann29 May 1999 01:36 
Michael Widenius31 May 1999 03:25 
Tim Bunce02 Jun 1999 03:04 
Michael Widenius02 Jun 1999 13:52 
Tim Bunce02 Jun 1999 19:24 
Michael Widenius03 Jun 1999 06:27 
Tim Bunce03 Jun 1999 07:15 
Subject:Re: Drivers giving different results
From:Tim Bunce (Tim.@ig.co.uk)
Date:06/02/1999 03:04:20 AM
List:com.mysql.lists.perl

On Mon, May 31, 1999 at 12:25:49PM +0200, Michael Widenius wrote:

Hi!

You can currently get the above behaviour if you add the flag CLIENT_FOUND_ROWS to the last argument of mysql_real_connect().

One problem is that ANY SQL server is allowed to optimize the query:

UPDATE foo SET col=col to UPDATE foo SET col=col WHERE col<>col

I think that one should strongly discourage the use of affected rows in the above manner as any SQL server may add the above optimisation in any updated version!

What makes you say that? Specifically. Is it specified somewhere in a standards document somewhere? (The word "affected" is, sadly, rather too ambiguous to be relied upon by itself.)

I know of no other SQL server that does that. Do you?

Tim.