1. 27 Jan, 2010 5 commits
  2. 25 Jan, 2010 3 commits
  3. 22 Jan, 2010 2 commits
  4. 21 Jan, 2010 3 commits
  5. 20 Jan, 2010 4 commits
  6. 19 Jan, 2010 5 commits
  7. 18 Jan, 2010 7 commits
  8. 17 Jan, 2010 1 commit
  9. 16 Jan, 2010 1 commit
    • unknown's avatar
      BUG#47418 RBR fails, failure with mixup of base/temporary/view · 377d7102
      unknown authored
      'CREATE TABLE IF NOT EXISTS ... SELECT' statement were causing 'CREATE
      TEMPORARY TABLE ...' to be written to the binary log in row-based 
      mode (a.k.a. RBR), when there was a temporary table with the same name.
      Because the 'CREATE TABLE ... SELECT' statement was executed as 
      'INSERT ... SELECT' into the temporary table. Since in RBR mode no 
      other statements related to temporary tables are written into binary log,
      this sometimes broke replication.
      
      This patch changes behavior of 'CREATE TABLE [IF NOT EXISTS] ... SELECT ...'.
      it ignores existence of temporary table with the 
      same name as table being created and is interpreted
      as attempt to create/insert into base table. This makes behavior of
      'CREATE TABLE [IF NOT EXISTS] ... SELECT' consistent with
      how ordinary 'CREATE TABLE' and 'CREATE TABLE ... LIKE' behave.
      377d7102
  10. 15 Jan, 2010 8 commits
    • Georgi Kodinov's avatar
      Bug #46175: NULL read_view and consistent read assertion · 7a7147c5
      Georgi Kodinov authored
      The optimizer must not continue executing the current query
      if e.g. the storage engine reports an error.
      This is somewhat hard to implement with Item::val_xxx()
      because they do not have means to return error code.
      This is why we need to check the thread's error state after
      a call to one of the Item::val_xxx() methods.
      
      Fixed store_key_item::copy_inner() to return an error state 
      if an error happened during the call to Item::save_in_field() 
      because it calls Item::val_xxx().
      Also added similar checks to related places.
      7a7147c5
    • Sergey Glukhov's avatar
      compilation failure fix · b6685d35
      Sergey Glukhov authored
      b6685d35
    • Sergey Glukhov's avatar
      backported: · 5a4a98af
      Sergey Glukhov authored
      -WL#2822 INFORMATION_SCHEMA.ROUTINES: Add missing columns
      -WL#2003 INFORMATION_SCHEMA: PARAMETERS view
      -addon for 'I_S optimization' WL
      
      5a4a98af
    • Alexey Kopytov's avatar
      Manual merge from mysql-5.1-bugteam into mysql-trunk-merge. · 0a5b406f
      Alexey Kopytov authored
      Conflicts:
      
      Text conflict in .bzr-mysql/default.conf
      Text conflict in mysql-test/suite/rpl/r/rpl_loaddata_fatal.result
      Text conflict in mysql-test/suite/rpl/r/rpl_stm_log.result
      Text conflict in mysql-test/t/mysqlbinlog.test
      Text conflict in sql/sql_acl.cc
      Text conflict in sql/sql_servers.cc
      Text conflict in sql/sql_update.cc
      Text conflict in support-files/mysql.spec.sh
      0a5b406f
    • Georgi Kodinov's avatar
      merge · 0305aea8
      Georgi Kodinov authored
      0305aea8
    • Georgi Kodinov's avatar
      merge of version change. · a07ca237
      Georgi Kodinov authored
      Added not_embedded to the new dbug_sync test file.
      a07ca237
    • unknown's avatar
      Fix for perfschema.binlog_stmt failure: · 5d279205
      unknown authored
              
      Problem: The test case failed because: (i) warning text in 
               result file differed from the warning output by the 
               server, and (ii) binlog contents in result file did
               not show the statements logged wrapped in BEGIN/COMMIT
               as it is the case after WL 2687.
            
      Solution: We update the result file, but first we change the
                unsafe warning text to also refer to performance_schema
                table(s). This required changing the result files for
                existing test cases that provide output for warnings 
                related to ER_BINLOG_UNSAFE_SYSTEM_TABLE. "Grepping" in
                result files, shows that only binlog_unsafe contained
                reference to such a warning.
            
                We also update the result file with the missing 
                BEGIN/COMMIT statements.
      5d279205
    • MySQL Build Team's avatar
  11. 14 Jan, 2010 1 commit