1. 01 Apr, 2009 2 commits
  2. 31 Mar, 2009 1 commit
  3. 30 Mar, 2009 5 commits
  4. 27 Mar, 2009 15 commits
    • Kristofer Pettersson's avatar
      Bug#40127 Multiple table DELETE IGNORE hangs on foreign key constraint violation · 137f1e1e
      Kristofer Pettersson authored
                on 5.0            
      The server crashes on an assert in net_end_statement indicating that the
      Diagnostics area wasn't set properly during execution.
      This happened on a multi table DELETE operation using the IGNORE keyword.
      The keyword is suppose to allow for execution to continue on a best effort
      despite some non-fatal errors. Instead execution stopped and no client
      response was sent which would have led to a protocol error if it hadn't been
      for the assert.
      This patch corrects this issue by checking for the existence of an IGNORE
      option before setting an error state during row-by-row delete iteration.
      137f1e1e
    • Staale Smedseng's avatar
      Merge from 5.0-bugteam · d186014c
      Staale Smedseng authored
      d186014c
    • Staale Smedseng's avatar
      Merge from 5.1-bugteam · 45753263
      Staale Smedseng authored
      45753263
    • Alexey Kopytov's avatar
      Automerge. · 7b006908
      Alexey Kopytov authored
      7b006908
    • Alexey Kopytov's avatar
      Automerge. · 3952372a
      Alexey Kopytov authored
      3952372a
    • Alexey Kopytov's avatar
      Automerge. · a37e4311
      Alexey Kopytov authored
      a37e4311
    • Staale Smedseng's avatar
      Merge from 5.0-bugteam · 70fdfcb6
      Staale Smedseng authored
      70fdfcb6
    • Staale Smedseng's avatar
      Bug#39953 Triggers are not working properly with multi table · fce11a8b
      Staale Smedseng authored
      updates
      
      Attempt to execute trigger or stored function with multi-UPDATE
      which used - but didn't update - a table that was also used by
      the calling statement led to an error. Read-only reference to
      tables used in the calling statement should be allowed.
       
      This problem was caused by the fact that check for conflicting
      use of tables in SP/triggers was performed in open_tables(),
      and in case of multi-UPDATE we didn't know exact lock type at
      this stage.
      
      We solve the problem by moving this check to lock_tables(), so
      it can be performed after exact lock types for tables used by
      multi-UPDATE are determined.
      fce11a8b
    • Alexey Kopytov's avatar
      Manual merge. · 94926217
      Alexey Kopytov authored
      94926217
    • Alexey Kopytov's avatar
      Fix for bug #43432: Union on floats does unnecessary rounding · afb2b6de
      Alexey Kopytov authored
        
      UNION could convert fixed-point FLOAT(M,D)/DOUBLE(M,D) columns  
      to FLOAT/DOUBLE when aggregating data types from the SELECT  
      substatements. While there is nothing particularly wrong with  
      this behavior, especially when M is greater than the hardware  
      precision limits, it could be confusing in cases when all  
      SELECT statements in a union have the same  
      FLOAT(M,D)/DOUBLE(M,D) columns with equal precision  
      specifications listed in the same position.  
        
      Since the manual is quite vague on what data type should be  
      returned in such cases, the bug was fixed by implementing the  
      most 'expected' behavior: do not convert FLOAT(M,D)/DOUBLE(M,D)  
      to anything else if all SELECT statements in a UNION have the  
      same precision for that column.  
      afb2b6de
    • Ramil Kalimullin's avatar
      Merge · 8d3aceb0
      Ramil Kalimullin authored
      8d3aceb0
    • Leonard Zhou's avatar
      Merge · 78bc692a
      Leonard Zhou authored
      78bc692a
    • Ramil Kalimullin's avatar
      Fix for bug #26288: savepoint not deleted, comit on empty transaction · 2005f3c7
      Ramil Kalimullin authored
      Problem: commit doesn't delete savepoints if there are no changes 
      in the transaction.
      
      Fix: delete them in such cases.
      2005f3c7
    • Leonard Zhou's avatar
      Merge · 75ab3274
      Leonard Zhou authored
      75ab3274
    • Leonard Zhou's avatar
      Merge 5.0 to 5.1 · dccca953
      Leonard Zhou authored
      dccca953
  5. 26 Mar, 2009 5 commits
    • Davi Arnaut's avatar
      Bug#33899: Deadlock in mysql_real_query with shared memory connections · 26f561d5
      Davi Arnaut authored
      The problem is that the read and write methods of the shared
      memory transport (protocol) didn't react to asynchornous close
      events, which could lead to a lock up as the client would wait
      (until time out) for a server response that will never come.
      
      The solution is to also wait for close events while waiting
      for I/O from or to the server.
      
      Bug report and patch submitted by: Armin Schöffmann
      26f561d5
    • Davi Arnaut's avatar
      Bug#33899: Deadlock in mysql_real_query with shared memory connections · bfa198c2
      Davi Arnaut authored
      The problem is that the read and write methods of the shared
      memory transport (protocol) didn't react to asynchronous close
      events, which could lead to a lock up as the client would wait
      (until time out) for a server response that will never come.
      
      The solution is to also wait for close events while waiting
      for I/O from or to the server.
      bfa198c2
    • Matthias Leich's avatar
      Fix for Bug#43383 main.variables-big : Weak testing code and result · 7a7885f4
      Matthias Leich authored
      including modifications according to code review
      + backport of the fix for
        Bug 41932 funcs_1: is_collation_character_set_applicability path
                           too long for tar
        which was missing in 5.0 (just a renaming of two files)
      7a7885f4
    • Leonard Zhou's avatar
      BUG#35515 Aliases of variables in binary log are ignored with NAME_CONST. · 8c5bba72
      Leonard Zhou authored
            
      When add an aliase name after NAME_CONST, the aliase name will be overwrite.
            
      NAME_CONST will re-set the field's name only if there isn't an aliase in the
      function fix-fields().
      If there is an aliase, NAME_CONST doesn't re-set the field's name and keeps the old
      name.
      8c5bba72
    • Leonard Zhou's avatar
      Merge · 9be507ca
      Leonard Zhou authored
      9be507ca
  6. 25 Mar, 2009 12 commits