List:Internals« Previous MessageNext Message »
From:jan.lindstrom Date:April 27 2005 8:19am
Subject:bk commit into 5.0 tree (jan:1.1887)
View as plain text  
Below is the list of changes that have just been committed into a local
5.0 repository of jan. When jan does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet
  1.1887 05/04/27 09:18:58 jan@stripped +1 -0
  Correct the comment. Consistent read is used only in INSERT...SELECT 
  without FOR UPDATE or IN SHARE MODE.

  sql/ha_innodb.cc
    1.196 05/04/27 09:18:49 jan@stripped +1 -3
    Correct the comment. Consistent read is used only in INSERT...SELECT 
    without FOR UPDATE or IN SHARE MODE.

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	jan
# Host:	hundin.mysql.fi
# Root:	/home/jan/orig/mysql-5.0

--- 1.195/sql/ha_innodb.cc	Tue Apr 19 09:38:11 2005
+++ 1.196/sql/ha_innodb.cc	Wed Apr 27 09:18:49 2005
@@ -6157,9 +6157,7 @@
 			option set and isolation level of the transaction
 			is not set to serializable and MySQL is doing
 			INSERT INTO...SELECT without FOR UPDATE or IN
-			SHARE MODE we use consistent read for select. 
-			Similarly, in case of DELETE...SELECT and
-			UPDATE...SELECT when these are not multi table.*/
+			SHARE MODE we use consistent read for select. */
 
 			prebuilt->select_lock_type = LOCK_NONE;
 			prebuilt->stored_select_lock_type = LOCK_NONE;
Thread
bk commit into 5.0 tree (jan:1.1887)jan.lindstrom27 Apr