1. 06 Jul, 2005 1 commit
  2. 05 Jul, 2005 2 commits
  3. 04 Jul, 2005 7 commits
  4. 03 Jul, 2005 2 commits
  5. 02 Jul, 2005 4 commits
  6. 01 Jul, 2005 9 commits
  7. 30 Jun, 2005 3 commits
  8. 29 Jun, 2005 3 commits
  9. 28 Jun, 2005 9 commits
    • unknown's avatar
      Merge sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1 · 87000dc2
      unknown authored
      into sanja.is.com.ua:/home/bell/mysql/bk/work-bug3-4.1
      
      87000dc2
    • unknown's avatar
      fixed not_null_tables() for IN() (BUG#9393) · b8e5174d
      unknown authored
      (IN() remove NULL rows only for tables from first argument (value which we looking for in IN() list) but not for tables from IN() list)
      Also it will be better change Item::not_null_tables() to prohibit this optimisation by default for new created items in 5.0 or 5.1.
      
      
      mysql-test/r/select.result:
        IN with outer join condition
      mysql-test/t/select.test:
        IN with outer join condition
      sql/item_cmpfunc.h:
        correct not_null_tables() for IN
      b8e5174d
    • unknown's avatar
      Merge marko@bk-internal.mysql.com:/home/bk/mysql-4.1 · 24d0d075
      unknown authored
      into hundin.mysql.fi:/home/marko/mysql-4.1
      
      24d0d075
    • unknown's avatar
      Merge ibabaev@bk-internal.mysql.com:/home/bk/mysql-4.1 · ef260b9e
      unknown authored
      into rurik.mysql.com:/home/igor/mysql-4.1
      
      ef260b9e
    • unknown's avatar
      Move reset of insert_values to ensure it's done also during error conditions · 5145698c
      unknown authored
      This fixed a failure of insert_update.test on some platforms
      
      
      mysys/thr_alarm.c:
        Fixed problem noticed by valgrind
      sql/opt_range.cc:
        Simple optimization for common case
      sql/sql_base.cc:
        Safety assert
      sql/sql_insert.cc:
        Added comment
      5145698c
    • unknown's avatar
      Merge rurik.mysql.com:/home/igor/mysql-4.1 · 1f02d17e
      unknown authored
      into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
      
      
      sql/sql_select.cc:
        Auto merged
      1f02d17e
    • unknown's avatar
      Merge ibabaev@bk-internal.mysql.com:/home/bk/mysql-4.1 · 9fdb9755
      unknown authored
      into rurik.mysql.com:/home/igor/mysql-4.1
      
      
      sql/field.cc:
        Auto merged
      sql/sql_select.cc:
        Auto merged
      9fdb9755
    • unknown's avatar
      group_by.result, group_by.test: · 1c2a96cc
      unknown authored
        Added a test case for bug #11414.
      sql_select.cc:
        Fixed bug #11414: crash on Windows with some simple
        GROUP BY queries.
        It happened to an allocation of an array containing
        0 Copy_field elements in setup_copy_fields.
        The bug had been already fixed in 5.0.
      
      
      sql/sql_select.cc:
        Fixed bug #11414: crash on Windows with some simple
        GROUP BY queries.
        It happened to an allocation of an array containing
        0 Copy_field elements in setup_copy_fields.
        The bug had been already fixed in 5.0.
      mysql-test/t/group_by.test:
        Added a test case for bug #11414.
      mysql-test/r/group_by.result:
        Added a test case for bug #11414.
      1c2a96cc
    • unknown's avatar
      ctype_ucs.result, ctype_ucs.test, ctype_utf8.result, ctype_utf8.test: · 216eba80
      unknown authored
        Fixing tests accordingly.
      ctype-ucs2.c:
        The same fix for UCS2.
      ctype-utf8.c:
        Bug #9557
        MyISAM utf8 table crash
        The problem was that my_strnncollsp_xxx could
        return big value in the range 0..0xffff.
        for some constant pairs it could return 32738,
        which is defined as MI_FOUND_WRONG_KEY in
        myisamdef.h. As a result, table considered to
        be crashed. 
        Fix to return -1,0 or 1.
      
      
      strings/ctype-utf8.c:
        Bug #9557
        MyISAM utf8 table crash
        The problem was that my_strnncollsp_xxx could
        return big value in the range 0..0xffff.
        for some constant pairs it could return 32738,
        which is defined as MI_FOUND_WRONG_KEY in
        myisamdef.h. As a result, table considered to
        be crashed. 
        Fix to return -1,0 or 1.
      strings/ctype-ucs2.c:
        The same fix for UCS2.
      mysql-test/t/ctype_utf8.test:
        Fixing tests accordingly.
      mysql-test/r/ctype_utf8.result:
        Fixing tests accordingly.
      mysql-test/t/ctype_ucs.test:
        Fixing tests accordingly.
      mysql-test/r/ctype_ucs.result:
        Fixing tests accordingly.
      216eba80