1. 31 Jan, 2007 1 commit
  2. 22 Jan, 2007 4 commits
  3. 18 Jan, 2007 7 commits
  4. 17 Jan, 2007 9 commits
  5. 16 Jan, 2007 1 commit
    • unknown's avatar
      A fix for the broken 4.1-runtime tree. · 4f70925b
      unknown authored
      
      mysql-test/t/backup.test:
        Backport a patch for sporadically failing myisam.test (and now ps.test)
        from 5.0. The cause was in backup.test not cleaning up tables in
        mysqltest-vardir/tmp after itself.
      mysql-test/t/ps.test:
        Add additional protection against possible failure in the middle of
        backup.test
      4f70925b
  6. 15 Jan, 2007 2 commits
    • unknown's avatar
      A post-merge fix. · e394ffc5
      unknown authored
      
      sql/sql_parse.cc:
        A post-merge fix (broken alter_table.test): restore Svoj's fix
        for Bug#23404 lost during merge.
      e394ffc5
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1-runtime · 8f28774b
      unknown authored
      into  bodhi.local:/opt/local/work/mysql-4.1-4968-to-push
      
      
      sql/mysql_priv.h:
        Auto merged
      sql/sql_class.h:
        Auto merged
      sql/sql_insert.cc:
        Auto merged
      sql/sql_parse.cc:
        Manual merge.
      sql/sql_table.cc:
        Manual merge.
      8f28774b
  7. 13 Jan, 2007 1 commit
    • unknown's avatar
      Fixed bug #24776: an assertion abort in handler::ha_index_init · fd72879e
      unknown authored
      for queries using 'range checked for each record'.
      The problem was fixed in 5.0 by the patch for bug 12291.
      This patch down-ported the corresponding code from 5.0 into 
      QUICK_SELECT::init() and added a new test case. 
      
      
      mysql-test/r/range.result:
        Added a test case for bug #24776.
      mysql-test/t/range.test:
        Added a test case for bug #24776.
      sql/opt_range.h:
        Fixed bug #24776: an assertion abort in handler::ha_index_init
        for queries using 'range checked for each record'.
        The problem was fixed in 5.0 by the patch for bug 12291.
        The patch for 4.1 down-ported the corresponding code from 5.0 into 
        QUICK_SELECT::init().
      fd72879e
  8. 12 Jan, 2007 4 commits
  9. 11 Jan, 2007 11 commits
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · 22c61cba
      unknown authored
      into  bodhi.local:/opt/local/work/mysql-4.1-runtime
      
      
      sql/item_func.cc:
        Auto merged
      22c61cba
    • unknown's avatar
      Merge mysqldev@production.mysql.com:my/mysql-4.0-15815 · 5429703b
      unknown authored
      into  trift2.:/MySQL/M40/mysql-4.0
      
      5429703b
    • unknown's avatar
      Merge mysqldev@quadxeon:/benchmarks/ext3/TOSAVE/tsmith/bk/g40 · 15ccfccf
      unknown authored
      into  mysql.com:/data0/mysqldev/my/mysql-4.0-15815
      
      15ccfccf
    • unknown's avatar
      Merge trift2.:/MySQL/M40/clone-4.0 · d85196e9
      unknown authored
      into  trift2.:/MySQL/M40/mysql-4.0
      
      d85196e9
    • unknown's avatar
      Merge kpdesk.mysql.com:/home/thek/dev/mysql-4.0-maint · b31d1b9f
      unknown authored
      into  kpdesk.mysql.com:/home/thek/dev/mysql-4.1-maint
      
      
      mysys/mf_iocache.c:
        Auto merged
      mysys/my_seek.c:
        Auto merged
      b31d1b9f
    • unknown's avatar
      Merge kpdesk.mysql.com:/home/thek/dev/test23010/my40-bug23010 · 0b1b48fa
      unknown authored
      into  kpdesk.mysql.com:/home/thek/dev/mysql-4.0-maint
      
      0b1b48fa
    • unknown's avatar
      Bug#23409: Arguments of the ENCODE() and the DECODE() functions were not printed · 49a469fe
      unknown authored
      correctly.
      
      The Item_func::print method was used to print the Item_func_encode and the
      Item_func_decode objects. The last argument to ENCODE and DECODE functions
      is a plain C string and thus Item_func::print wasn't able to print it.
      
      The print() method is added to the Item_func_encode class. It correctly
      prints the Item_func_encode and the Item_func_decode objects.
      
      
      mysql-test/t/func_str.test:
        Added a test case for bug#23409: Arguments of the ENCODE() and the
        > DECODE() functionswere not printed correctly.
      mysql-test/r/func_str.result:
        Added a test case for bug#23409: Arguments of the ENCODE() and the DECODE() functions were not printed correctly.
      sql/item_strfunc.h:
        Bug#23409: Arguments of the ENCODE() and the DECODE() functions were not printed correctly.
        The print() method is added to the Item_func_encode class.
      sql/item_strfunc.cc:
        Bug#23409: Arguments of the ENCODE() and the DECODE() functions were not printed correctly.
        The print() method is added to the Item_func_encode class. It correctly
        prints the Item_func_encode and the Item_func_decode objects.
      49a469fe
    • unknown's avatar
      Merge fix for bug#17711 · 2deb406b
      unknown authored
      2deb406b
    • unknown's avatar
      Merge kpettersson@bk-internal:/home/bk/mysql-4.1-maint · aaef5d4c
      unknown authored
      into  kpdesk.mysql.com:/home/thek/dev/mysql-4.1-maint
      
      
      mysys/mf_iocache.c:
        Auto merged
      aaef5d4c
    • unknown's avatar
      Bug#17711: DELETE doesn't use index when ORDER BY, LIMIT and non-restricting · 5a598b55
      unknown authored
      WHERE is present.
      
      If a DELETE statement with ORDER BY and LIMIT contains a WHERE clause
      with conditions that for sure cannot be used for index access (like in
      WHERE @var:= field) the execution always follows the filesort path.    
      It happens currently even when for the above case there is an index that
      can be used to speedup sorting by the order by list.
      
      Now if a DELETE statement with ORDER BY and LIMIT contains such WHERE
      clause conditions that cannot be used to build any quick select then
      the mysql_delete() tries to use an index like there is no WHERE clause at all.
      
      
      mysql-test/t/delete.test:
        Added a test case for bug#17711: DELETE doesn't use index when ORDER BY, LIMIT and non-restricting
        WHERE is present.
      mysql-test/r/delete.result:
        Added a test case for bug#17711: DELETE doesn't use index when ORDER BY, LIMIT and non-restricting WHERE is present.
      sql/sql_delete.cc:
        Bug#17711: DELETE doesn't use index when ORDER BY, LIMIT and non-restricting WHERE is present.
        Now if a DELETE statement with ORDER BY and LIMIT contains such WHERE
        clause conditions that cannot be used to build any quick select then
        the mysql_delete() tries to use an index like there is no WHERE clause at all.
      5a598b55
    • unknown's avatar
      Merge kpdesk.mysql.com:/home/thek/dev/mysql-4.0-maint · 34f7ba87
      unknown authored
      into  kpdesk.mysql.com:/home/thek/dev/mysql-4.1-maint
      
      
      mysys/mf_iocache.c:
        Auto merged
      mysys/my_read.c:
        Auto merged
      mysys/my_seek.c:
        Auto merged
      34f7ba87