List:Commits« Previous MessageNext Message »
From:Ingo Struewing Date:December 17 2009 10:59am
Subject:bzr commit into mysql-5.6-next-mr-bugfixing branch
(ingo.struewing:2932) Bug#43568 WL#3561
View as plain text  
#At file:///home2/mydev/bzrroot/mysql-5.6-wl3561-2/ based on revid:ingo.struewing@stripped

 2932 Ingo Struewing	2009-12-17
      WL#3561 - transactional LOCK TABLE
      Backport.
      Backported revision revid:kristofer.pettersson@stripped
        Bug#43568 set_handler_table_locks uses parser tokens instead 
                  of correct lock_options
        
        set_handler_table_locks uses parser tokens instead of correct
        lock options to determine the correct lock to set.
        After open_tables, the correct lock option is stored in
        TABLE::reginfo.lock_type.
        Failing to use the correct lock option might create issues with
        binlog and replication.
      Most changes have been included in the first patch already.
     @ include/thr_lock.h
        WL#3561 - transactional LOCK TABLE
        Backport.
          Bug#43568 set_handler_table_locks uses parser tokens instead 
                    of correct lock_options
          * Added comment.

    modified:
      include/thr_lock.h
=== modified file 'include/thr_lock.h'
--- a/include/thr_lock.h	2009-04-14 12:05:32 +0000
+++ b/include/thr_lock.h	2009-12-17 10:59:24 +0000
@@ -27,7 +27,11 @@ extern "C" {
 struct st_thr_lock;
 extern ulong locks_immediate,locks_waited ;
 
-/*
+/**
+  Lock types are used to request a lock on a table. Changes in this enumeration
+  might affect transactional locks as well.
+  @see set_handler_table_locks
+  @see read_lock_type_for_table
   Important: if a new lock type is added, a matching lock description
              must be added to sql_test.cc's lock_descriptions array.
 */


Attachment: [text/bzr-bundle] bzr/ingo.struewing@sun.com-20091217105924-5u66u1szwpx84bf8.bundle
Thread
bzr commit into mysql-5.6-next-mr-bugfixing branch(ingo.struewing:2932) Bug#43568 WL#3561Ingo Struewing17 Dec