1. 07 Apr, 2006 1 commit
    • aelkin@mysql.com's avatar
      Bug#17284 erroneous temp table cleanup on slave. · d881fb36
      aelkin@mysql.com authored
        
           Idea of the fix is for master to send FD event with `created' as 0
           to reconnecting slave (upon slave_net_timeout, no master crash) to avoid destroying temp tables.
           In a case of a connect by slave to the master after its crash temp tables have been already
           cleaned up so that slave can not keep `orphan' temp tables.
      d881fb36
  2. 04 Apr, 2006 8 commits
  3. 03 Apr, 2006 8 commits
  4. 02 Apr, 2006 1 commit
  5. 01 Apr, 2006 13 commits
  6. 31 Mar, 2006 6 commits
    • kent@mysql.com's avatar
      Makefile.am, yassl.m4: · f5a9cc17
      kent@mysql.com authored
        Enable automake to determine dependency on yaSSL, by explicitly
        listing the .la files in Makefile.am, instead of using
        'yassl_libs_with_path', bug#18273
      f5a9cc17
    • aivanov@mysql.com's avatar
      Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-5.0 · 99f7292b
      aivanov@mysql.com authored
      into  mysql.com:/home/alexi/innodb/mysql-5.0-merged
      99f7292b
    • aivanov@mysql.com's avatar
      Applied innodb-5.0-ss398 snapshot. · 771fb26e
      aivanov@mysql.com authored
       Fixed BUG#15650: DELETE with LEFT JOIN crashes server
       with innodb_locks_unsafe_for_binlog.
       Fixed compilation problem with non-C99 compilers
       in btr0sea.c
      771fb26e
    • timour@mysql.com's avatar
      Fixed a typo. · efdc2fd1
      timour@mysql.com authored
      efdc2fd1
    • timour@mysql.com's avatar
      Merge mysql.com:/home/timka/mysql/src/5.0-virgin · b85bd1e8
      timour@mysql.com authored
      into  mysql.com:/home/timka/mysql/src/5.0-bug-16710
      b85bd1e8
    • timour@mysql.com's avatar
      Fix for BUG#16710. · eed7cf09
      timour@mysql.com authored
      The bug was due to a missed case in the detection of whether an index
      can be used for loose scan. More precisely, the range optimizer chose
      to use loose index scan for queries for which the condition(s) over
      an index key part could not be pushed to the index together with the
      loose scan.
      
      As a result, loose index scan was selecting the first row in the
      index with a given GROUP BY prefix, and was applying the WHERE
      clause after that, while it should have inspected all rows with
      the given prefix, and apply the WHERE clause to all of them.
      
      The fix detects and skips such cases.
      eed7cf09
  7. 30 Mar, 2006 3 commits