1. 02 Mar, 2007 3 commits
  2. 01 Mar, 2007 15 commits
  3. 28 Feb, 2007 9 commits
  4. 27 Feb, 2007 6 commits
    • rafal@quant.(none)'s avatar
      Merge quant.(none):/ext/mysql/bkroot/mysql-5.0-rpl · 235ca912
      rafal@quant.(none) authored
      into  quant.(none):/ext/mysql/bk/mysql-5.0-bug25306
      235ca912
    • lars/lthalmann@mysql.com/dl145j.mysql.com's avatar
      Merge mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge · 6889569f
      into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
      6889569f
    • lars/lthalmann@mysql.com/dl145h.mysql.com's avatar
      Merge mysql.com:/nfsdisk1/lars/bkroot/mysql-5.0-rpl · f872d8ff
      into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
      f872d8ff
    • cbell/Chuck@mysql_cab_desk.'s avatar
      BUG#20141 "User-defined variables are not replicated properly for · d13c3b94
      cbell/Chuck@mysql_cab_desk. authored
                SF/Triggers in SBR mode."
      BUG#14914 "SP: Uses of session variables in routines are not always replicated"
      BUG#25167 "Dupl. usage of user-variables in trigger/function is not replicated
                correctly"
      
      This patch corrects a minor error in the previous patch for BUG#20141. This patch
      corrects an errant code change to sp_head.cc. The comments for the first patch follow:
      
      User-defined variables used inside of stored functions/triggers in
      statements which did not update tables directly were not replicated.
      We also had problems with replication of user-defined variables which
      were used in triggers (or stored functions called from table-updating
      statements) more than once.
      
      This patch addresses the first issue by enabling logging of all
      references to user-defined variables in triggers/stored functions
      and not only references from table-updating statements.
      
      The second issue stemmed from the fact that for user-defined
      variables used from triggers or stored functions called from
      table-updating statements we were writing binlog events for each
      reference instead of only one event for the first reference.
      This problem is already solved for stored functions called from
      non-updating statements with help of "event unioning" mechanism.
      So the patch simply extends this mechanism to the case affected.
      It also fixes small problem in this mechanism which caused wrong
      logging of references to user-variables in cases when non-updating
      statement called several stored functions which used the same
      variable and some of these function calls were omitted from binlog
      as they were not updating any tables.
      d13c3b94
    • bar@mysql.com's avatar
      Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-5.0-rpl · 75177d9c
      bar@mysql.com authored
      into  mysql.com:/home/bar/mysql-5.0.b24478
      75177d9c
    • gluh@mysql.com/eagle.(none)'s avatar
      removed unused variable · b3cb8466
      gluh@mysql.com/eagle.(none) authored
      b3cb8466
  5. 26 Feb, 2007 6 commits
  6. 25 Feb, 2007 1 commit
    • evgen@sunlight.local's avatar
      item.h: · e91347dd
      evgen@sunlight.local authored
        Post fix for bug#23800.
        Copy the table name of an Item_outer_ref to the conventional memory.
      e91347dd