1. 12 Mar, 2009 1 commit
  2. 10 Mar, 2009 4 commits
  3. 09 Mar, 2009 15 commits
  4. 06 Mar, 2009 6 commits
    • Tatiana A. Nurnberg's avatar
      manual merge · cee070e1
      Tatiana A. Nurnberg authored
      cee070e1
    • Matthias Leich's avatar
      2417d310
    • Kristofer Pettersson's avatar
      Manual merge · 55c779cd
      Kristofer Pettersson authored
      55c779cd
    • He Zhenxing's avatar
      5229ef4a
    • He Zhenxing's avatar
      Auto merge · 37068efd
      He Zhenxing authored
      37068efd
    • He Zhenxing's avatar
      BUG#22082 Slave hangs(holds mutex) on "disk full" · 82fc3547
      He Zhenxing authored
      When disk is full, server may waiting for free space while
      writing binlog, relay-log or MyISAM tables. The server will 
      continue after user have freed some space. But the error
      message printed was not quite clear about the how often the
      error message is printed, and there will be a delay before
      the server continue and user freeing space. And caused users
      thinking that the server was hanging forever.
      
      This patch fixed the problem by making the error messages
      printed more clear. The error message is split into two part,
      the first part will only be printed once, and the second part
      will be printed very 10 times.
      
      Message first part:
      Disk is full writing '<filename>' (Errcode: <errorno>). Waiting
      for someone to free space... (Expect up to 60 secs delay for 
      server to continue after freeing disk space)
      
      Message second part:
      Retry in 60 secs, Message reprinted in 600 secs
      82fc3547
  5. 05 Mar, 2009 10 commits
    • Luis Soares's avatar
      BUG#39753: Replication failure on MIXED + bit + myisam + no PK · 58339038
      Luis Soares authored
                                
      When using mixed mode the record values stored inside the storage
      engine differed from the ones computed from the row event. This
      happened because the prepare_record function was calling
      empty_record macro causing some don't care bits to be left set.
                                
      Replacing the empty_record plus explicitly setting defaults with 
      restore_record to restore the record default values fixes this.                          
      58339038
    • Tatiana A. Nurnberg's avatar
      Bug#40657: assertion with out of range variables and traditional sql_mode · 13328b0f
      Tatiana A. Nurnberg authored
      Some changes that make things more elegant in 6.0,
      backported so the code is mostly the same in 5.1,
      for easier maintainence.
      
      sql/set_var.cc:
        Backporting some changes to 5.1 so the code is
        mostly the same in both versions. Less to learn!
      13328b0f
    • Matthias Leich's avatar
      Merge of fix for Bug#42003 and Bug#43114 into more actual GCA tree · 0183d4d8
      Matthias Leich authored
      modifications according to the reviews are included
      0183d4d8
    • Sergey Glukhov's avatar
      removed unused variable · abfe3437
      Sergey Glukhov authored
      abfe3437
    • Kristofer Pettersson's avatar
      Bug#40363 Bug 20023 is not fixed on 5.0 · ac821c65
      Kristofer Pettersson authored
      This is a back port from 5.1 to 5.0.
      
      Fix for BUG 20023: mysql_change_user() resets the value
      of SQL_BIG_SELECTS.
        
      The bug was that SQL_BIG_SELECTS was not properly set
      in COM_CHANGE_USER.
        
      The fix is to update SQL_BIG_SELECTS properly.
      
      
      
      sql/sql_class.cc:
        Update THD::options with the respect to SQL_BIG_SELECTS
        in COM_CHANGE_USER.
      tests/mysql_client_test.c:
        Add a test case BUG#20023.
      ac821c65
    • Sergey Glukhov's avatar
      automerge · aa5441e1
      Sergey Glukhov authored
      aa5441e1
    • Guangbao Ni's avatar
      Auto merged · d65f6b54
      Guangbao Ni authored
      d65f6b54
    • Guangbao Ni's avatar
      BUG#41980 SBL, INSERT .. SELECT .. LIMIT = ERROR, even when @@SQL_LOG_BIN is 0 ! · 4f0f021c
      Guangbao Ni authored
            
      When binlog_format is STATEMENT and the statement is unsafe before,
      the unsafe warning/error message was issued without checking
      whether the SQL_LOG_BIN was turned on or not.
            
      Fixed with adding a sql_log_bin_toplevel flag in THD to check
      whether SQL_LOG_BIN is ON in current session whatever the current is in sp or not.
      
      
      mysql-test/suite/binlog/r/binlog_unsafe.result:
        Test case result for unsafe warning/error message
      mysql-test/suite/binlog/t/binlog_unsafe.test:
        Test case for unsafe message warning/error
      sql/set_var.cc:
        Adding a function set_option_log_bin_bit() which specailly handles to
        the change of SQL_LOG_BIN bit in order to set sql_log_bin_toplevel
        according to SQL_LOG_BIN current value at the same time.
      sql/sql_class.cc:
        Initialize the flag sql_log_bin_toplevel in THD::init(),
        and add the condition to check whether unsafe ror message was issued.
      sql/sql_class.h:
        Add a sql_log_bin_toplevel flag in THD to indicate whether the toplevel SQL_LOG_BIN is
      4f0f021c
    • Sergey Glukhov's avatar
      Bug#41030 Wrong meta data (incorrect fieldlen) · 3ef86918
      Sergey Glukhov authored
      set user variable max length on
      fix_length_and_dec() stage
      using real value length.
      
      
      mysql-test/r/variables.result:
        test result
      mysql-test/t/variables.test:
        test case
      sql/item_func.cc:
        set user variable max length on
        fix_length_and_dec() stage
        using real value length.
      3ef86918
    • Davi Arnaut's avatar
      Bug#41465: confusing error message when comment is too long · 53802ae6
      Davi Arnaut authored
      The problem was that the server was trying to use the unknown
      error format string (ER_UNKNOWN_ERROR) to print messages about
      comments being too long, but the said format string does not
      accept arguments and will always default to "Unknown error".
      
      The solution is to introduce new error messages which are
      specific to the error conditions so that server wants to
      signal -- this also means that it's possible to translate
      those messages.
      
      mysql-test/r/strict.result:
        Update test case result.
      mysql-test/t/strict.test:
        Update test case with new errors.
      sql/share/errmsg.txt:
        Introduce new errors for long comments.
      sql/unireg.cc:
        Use new errors.
      53802ae6
  6. 06 Mar, 2009 3 commits
  7. 05 Mar, 2009 1 commit