← Back to team overview

drizzle-discuss team mailing list archive

Re: Feedback on transaction_log behavior - non-updating UPDATE

 

Hi!

Sounds right to me.

Cheers,	
	-Brian

On Jun 30, 2010, at 2:20 PM, Patrick Crews wrote:

> Hi everyone,
> 
> Just wanting some clarification / discussion regarding what correct behavior for the transaction log should be for the case of an UPDATE statement that does nothing:
> 
> #Testing no UPDATE 
> DROP TABLE IF EXISTS t1 ;
> CREATE TABLE t1(a INT NOT NULL AUTO_INCREMENT, b INT NOT NULL, PRIMARY KEY(a));
> INSERT INTO t1 (b) VALUES (10),(20),(30),(40),(50),(60);
> UPDATE t1 SET b=10 WHERE a=1;
> 
> For the queries above, the UPDATE does nothing and is not logged by the transaction log at all.
> 
> While this does make sense, I wanted to make sure it is acceptable and to see if it should extend to all queries that cause no changes to be made.
> 
> Thanks for any feedback,
> Patrick
> _______________________________________________
> Mailing list: https://launchpad.net/~drizzle-discuss
> Post to     : drizzle-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~drizzle-discuss
> More help   : https://help.launchpad.net/ListHelp




References