1. 21 Oct, 2009 1 commit
    • Alexander Nozdrin's avatar
      Backporting WL#3953 from 6.0. Original revision: · 6756b0fc
      Alexander Nozdrin authored
      ```---------------------------------------------------------
      revno: 2476.714.9
      committer: markleith@medusa.mysql.com
      timestamp: Mon 2007-09-03 23:18:50 +0100
      message:
        Bug#25822 / WL#3953 - Log Access Denied errors for bad passwords in the error log
        
        Added logging of Access Denied messages on failed new connections to the 
        error log when log-warnings = 2.
        
        This allows a user to log these messages without having to incur the overhead
        of using the general query log on production systems.
      ```
      
      ---------------------------------------------------------
      6756b0fc
  2. 20 Oct, 2009 2 commits
    • Evgeny Potemkin's avatar
      Auto-merged fix for the bug#41760. · ad68fa65
      Evgeny Potemkin authored
      ad68fa65
    • Evgeny Potemkin's avatar
      #41760 Inserting into multiple-table views is not working · 4349a472
      Evgeny Potemkin authored
      During insert, we are not reading the rows in a referring table but
      instead using the last read row that happens to be in table->record[0].
      
      Now INSERT into such view is denied. 
      
      
      mysql-test/r/delayed.result:
        A test case result is adjusted after fixing bug#41760.
      mysql-test/r/insert.result:
        A test case result is adjusted after fixing bug#41760.
      mysql-test/t/delayed.test:
        A test case is adjusted after fixing bug#41760.
      mysql-test/t/insert.test:
        A test case is adjusted after fixing bug#41760.
      4349a472
  3. 19 Oct, 2009 6 commits
    • Guilhem Bichot's avatar
      Back-port from 6.0 of the fix for · 70fab22c
      Guilhem Bichot authored
      BUG#41759: "Valgrind warning: Invalid read of size 1 open_tables() with ps-protocol"
      (from revid:sergefp@mysql.com-20081227013233-f9n2by8romt37hyi)
      70fab22c
    • Guilhem Bichot's avatar
      Back-port from 6.0 of the fix for · 3088f6c7
      Guilhem Bichot authored
      BUG#38049 "incorrect rows estimations with references from preceding table"
      (from revid:sergefp@mysql.com-20090126194259-ue20il3qro529l4d).
      Compared to 6.0 where EXPLAIN indicates "Using index condition", here in join_optimizer.result
      we see "Using where"; it's normal; 6.0 shows the same if disabling Index Condition Pushdown.
      3088f6c7
    • Sergei Golubchik's avatar
      Bug#34374 mysql generates incorrect warning · 425c5ecd
      Sergei Golubchik authored
      backport to next-mr
      425c5ecd
    • Sergei Golubchik's avatar
      bug#34741 prepared show master logs without binlogging debug assert · c761cdc7
      Sergei Golubchik authored
      s/return/DBUG_RETURN/
      c761cdc7
    • Evgeny Potemkin's avatar
      Auto-merged fix for the bug#30302. · 3dcd5e73
      Evgeny Potemkin authored
      3dcd5e73
    • Evgeny Potemkin's avatar
      Bug#30302: Tables that were optimized away are printed in the · 60fc8507
      Evgeny Potemkin authored
      EXPLAIN EXTENDED warning.
      
      Query optimizer searches for the constant tables and optimizes them away. This
      means that fields of such tables are substituted for their values and on later
      phases they are treated as constants. After this constant tables are removed
      from the query execution plan. Nevertheless constant tables were shown in 
      the EXPLAIN EXTENDED warning thus producing query that might be not an
      equivalent of the original query.
              
      Now the print_join function skips all tables that were optimized away from
      printing to the EXPLAIN EXTENDED warning. If all tables were optimized away it
      produces the 'FROM dual' clause.
      
      
      mysql-test/r/explain.result:
        A test case added for the bug#30302.
      mysql-test/r/func_default.result:
        Adjusted test case result after fix for the bug#30302.
      mysql-test/r/func_regexp.result:
        Adjusted test case result after fix for the bug#30302.
      mysql-test/r/func_test.result:
        Adjusted test case result after fix for the bug#30302.
      mysql-test/r/having.result:
        Adjusted test case result after fix for the bug#30302.
      mysql-test/r/select.result:
        Adjusted test case result after fix for the bug#30302.
      mysql-test/r/subselect.result:
        Adjusted test case result after fix for the bug#30302.
      mysql-test/r/subselect3.result:
        Adjusted test case result after fix for the bug#30302.
      mysql-test/r/type_datetime.result:
        Adjusted test case result after fix for the bug#30302.
      mysql-test/t/explain.test:
        A test case added for the bug#30302.
      sql/sql_select.cc:
        Bug#30302: Tables that were optimized away are printed in the
        EXPLAIN EXTENDED warning.
        Now the print_join function skips all tables that were optimized away from
        printing to the EXPLAIN EXTENDED warning. If all tables were optimized away it
        produces the 'FROM dual' clause.
      sql/table.h:
        Adjusted test case result after fix for the bug#30302.
        The optimized_away flag is added to the TABLE_LIST struct.
      60fc8507
  4. 15 Oct, 2009 1 commit
  5. 14 Oct, 2009 3 commits
  6. 13 Oct, 2009 1 commit
    • Gleb Shchepa's avatar
      Backport of fix to bug #33629 into mysql-next-mr-bugfixing. · 1360ca09
      Gleb Shchepa authored
      Bug #33629: last_day function can return null, but has 'not null' flag set for result
      
      LAST_DAY and MAKEDATE functions are documented as
      returning NULL value, but actually they was implemented
      as returning NOT NULL typed values.
      
      That caused a confusing error "ERROR 1048 (23000): Column
      '...' cannot be null" on queries like: 
      
        SELECT 1 FROM (SELECT LAST_DAY('0')) a;
      
      
      mysql-test/r/func_sapdb.result:
          Updated test case for bug #33629.
      mysql-test/r/func_time.result:
          Updated test case for bug #33629.
      mysql-test/r/type_date.result:
          Added test case for bug #33629.
      mysql-test/t/type_date.test:
          Added test case for bug #33629.
      sql/item_timefunc.h:
          Bug #33629: last_day function can return null, but has 'not null' flag set for result
          
          1. The Item_func_makedate::fix_length_and_dec method
             has been modified to declare MAKEDATE() as a function
             returning nullable value.
          2. The Item_func_last_day::fix_length_and_dec method
             has been overloaded for the same purpose.
      1360ca09
  7. 12 Oct, 2009 2 commits
  8. 09 Oct, 2009 16 commits
  9. 08 Oct, 2009 4 commits
  10. 07 Oct, 2009 4 commits
    • Alexander Nozdrin's avatar
      A backport of a patch for Bug#35297. · 63e50788
      Alexander Nozdrin authored
      Original revision in mysql-6.0-codebase is:
      
      revno: 2617.31.14
      committer: Konstantin Osipov <kostja@sun.com>
      branch nick: mysql-6.0-runtime
      timestamp: Sat 2009-03-28 11:42:55 +0300
      message:
        Bug#35297 SHOW CREATE EVENT does not show the DEFINER:
        update test result after a merge from now.
      63e50788
    • Alexander Nozdrin's avatar
      A backport a patch of Bug#34828. · 5281fa36
      Alexander Nozdrin authored
      Original revision is from mysql-6.0-codebase:
      
      revno: 2617.23.13
      committer: Alexander Nozdrin <alik@sun.com>
      branch nick: 6.0-rt-bug34828
      timestamp: Tue 2009-02-24 14:25:46 +0300
      message:
        A patch for Bug#34828: OF is taken as OFF and a value of 0
        is set for variable SQL_notes.
        
        The problem was that partial match was allowed for keywords.
        
        A fix is to disable partial match and require full match.
      5281fa36
    • Alexander Nozdrin's avatar
      A backport of patch for Bug#26704. · 93848350
      Alexander Nozdrin authored
      Original revision is from mysql-6.0-codebase:
      
      revno: 2630.3.1
      committer: Alexander Nozdrin <alik@mysql.com>
      branch nick: 6.0-rt-bug26704
      timestamp: Thu 2008-05-29 21:04:06 +0400
      message:
        A fix for Bug#26704: Failing DROP DATABASE brings
        mysql-client out of sync.
      
        The problem was that we changed current database w/o caring
        whether it was dropped successfully or not.
      
        The fix is not to change current database if we failed to drop it.
      93848350
    • Alexander Nozdrin's avatar
      Merge from mysql-trunk-bugfixing. · 1733a974
      Alexander Nozdrin authored
      1733a974