1. 13 Jan, 2006 1 commit
  2. 06 Jan, 2006 3 commits
  3. 05 Jan, 2006 6 commits
  4. 04 Jan, 2006 10 commits
  5. 03 Jan, 2006 1 commit
  6. 31 Dec, 2005 1 commit
  7. 29 Dec, 2005 5 commits
  8. 28 Dec, 2005 10 commits
  9. 27 Dec, 2005 3 commits
    • ingo@mysql.com's avatar
      Merge istruewing@bk-internal.mysql.com:/home/bk/mysql-5.0 · bd1b724b
      ingo@mysql.com authored
      into  mysql.com:/home/mydev/mysql-5.0-bug5390
      bd1b724b
    • pekka@mysql.com's avatar
      Merge pnousiainen@bk-internal.mysql.com:/home/bk/mysql-5.0 · 76bdccd0
      pekka@mysql.com authored
      into  mysql.com:/space/pekka/ndb/version/my50
      76bdccd0
    • evgen@moonbone.local's avatar
      Fix bug#14583 · d91cbf34
      evgen@moonbone.local authored
      When InnoDB compares varchar field in ucs2 with given key using bin collation,
      it calls my_strnncollsp_ucs2_bin() to perform comparison.
      Because field length was lesser than length of key field should be padded
      with trailing spaces in order to get correct result. 
      Because  my_strnncollsp_ucs2_bin() was calling my_strnncollp_ucs2_bin(), which
      doesn't pads field, wrong comparison result was returned. This results in
      wrong result set.
      
      my_strnncollsp_ucs2_bin() now compares fields like my_strnncollsp_ucs2 do,
      but using binary collation.
      d91cbf34