1. 19 Oct, 2006 1 commit
    • unknown's avatar
      Fix for bug #20732: Partial index and long sjis search with '>' fails sometimes · 09ed9309
      unknown authored
      We miss some records sometimes using RANGE method if we have
      partial key segments.
      Example:
        Create table t1(a char(2), key(a(1)));
        insert into t1 values ('a'), ('xx');
        select a from t1 where a > 'x';
      We call index_read() passing 'x' key and HA_READ_AFTER_KEY flag
      in the handler::read_range_first() wich is wrong because we have
      a partial key segment for the field and might miss records like 'xx'.
      
      Fix: don't use open segments in such a case.
      
      
      mysql-test/r/range.result:
        Fix for bug #20732: Partial index and long sjis search with '>' fails sometimes
          - test result.
      mysql-test/t/range.test:
        Fix for bug #20732: Partial index and long sjis search with '>' fails sometimes
          - test case.
      sql/opt_range.cc:
        Fix for bug #20732: Partial index and long sjis search with '>' fails sometimes
          - check if we have a partial key segment for a Item_func::GT_FUNC;
            if so, don't set NEAR_MIN flag in order to use HA_READ_KEY_OR_NEXT
            instead of HA_READ_AFTER_KEY.
      sql/opt_range.h:
        Fix for bug #20732: Partial index and long sjis search with '>' fails sometimes
          - key segment 'flag' slot added.
      sql/sql_select.cc:
        Fix for bug #20732: Partial index and long sjis search with '>' fails sometimes
          - test (HA_PART_KEY_SEG | HA_NULL_PART) as we split it in the sql/table.cc
      sql/table.cc:
        Fix for bug #20732: Partial index and long sjis search with '>' fails sometimes
          - set HA_NULL_PART flag instead of HA_PART_KEY_SEG in order not to mix them.
      09ed9309
  2. 14 Oct, 2006 5 commits
  3. 13 Oct, 2006 9 commits
  4. 12 Oct, 2006 11 commits
  5. 11 Oct, 2006 13 commits
    • unknown's avatar
      Fixes for embedded server test · 6efe4250
      unknown authored
      
      client/mysqltest.c:
        Fix typo
      6efe4250
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1-maint · a24bebd3
      unknown authored
      into  polly.local:/home/kaa/src/maint/m41-maint--07OGk
      
      a24bebd3
    • unknown's avatar
      mtr_im_stop returns 1 if all is well · 326f9df2
      unknown authored
      326f9df2
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1-maint · cf39c821
      unknown authored
      into  polly.local:/home/kaa/src/maint/m41-maint--07OGk
      
      
      sql/item_timefunc.cc:
        Auto merged
      cf39c821
    • unknown's avatar
      Improve restart logic all code to detect restart is now in the functions · d19cb6dd
      unknown authored
      'run_testcase_need_master/slave_restart'
      Remove the faulty qw
      Only look for mysql_fix_privilege_tables if not windows
      
      
      mysql-test/lib/mtr_cases.pl:
        Move all code to determine when to restart into 'run_testcase_need_master/slave_restart' 
        Add possibility to wite --force-restart in -master.opt file, this will force a restart and
        since master is not started with any special options there is no need to restart
        again afterwards.
      mysql-test/mysql-test-run.pl:
        Remove the qw surrounding ENV{'LD_LIBRARY_PATH'}
        Only look for the sh script mysql_fix_privileges when not on windows
        Remove warnings about using unitialized variables
        Improve the restart logic, eall code to determine when to restart is
        now in run_testcase_need_master_restart and run_testcase_need_slave_restart
      mysql-test/t/bdb-alter-table-2-master.opt:
        Use --force-restart
      mysql-test/t/not_embedded_server-master.opt:
        Use --force-restart
      d19cb6dd
    • unknown's avatar
      Merge ahristov@bk-internal.mysql.com:/home/bk/mysql-4.1-maint · 4f644b4e
      unknown authored
      into  example.com:/work/bug23074/my41-bug23074
      
      4f644b4e
    • unknown's avatar
      Cset exclude: Kristofer.Pettersson@naruto.|ChangeSet|20060922092201|15946 · 3b8f5a27
      unknown authored
      
      sql/item_timefunc.cc:
        Exclude
      3b8f5a27
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1-maint · 282e7350
      unknown authored
      into  polly.local:/home/kaa/src/maint/m41-maint--07OGk
      
      
      sql/item_timefunc.cc:
        Auto merged
      282e7350
    • unknown's avatar
      Merge polly.local:/tmp/maint/bug11655/my41-bug11655 · 0e371de9
      unknown authored
      into  polly.local:/home/kaa/src/maint/m41-maint--07OGk
      
      
      sql/field.cc:
        Auto merged
      sql/item_timefunc.cc:
        Auto merged
      mysql-test/r/func_time.result:
        Manually merged
      mysql-test/t/func_time.test:
        Manually merged
      0e371de9
    • unknown's avatar
      Fix some bad code in mysqltest.c which cause segfault · 389e04b6
      unknown authored
      
      client/mysqltest.c:
        Remove vsnprintf() and DBUG_PRINT from die() function, as it's not portable to Windows, and it's not allowed to
        call vsnprintf() and then vfprintf() with the same args.
        Can't just print the buffer here, because the buffer is a fixed size.
        If the message is longer than will fit int he buffer, it would get
        truncated on Unix, and the full thing would be printed on Windows.
        This DBUG_PRINT isn't important enough for this hassle, so just get rid
        of it.
      389e04b6
    • unknown's avatar
      Fix a typo regarding checking whether HA_VAR_LENGTH_KEY is · e9c46520
      unknown authored
      set. This has always worked because when flag is !=0 then
      HA_VAR_LENGTH_KEY is always set. Therefore, a test case cannot
      reveal a faulty behavior.
      
      Fix for bug#23074: typo in myisam/sort.c
      
      
      myisam/sort.c:
        fix typo. Nevertheless, it has worked as expected
        because when a bit in flag is set HA_VAR_LENGTH_KEY has
        been always set too. Actually, no problem exposed through
        DDL.
      e9c46520
    • unknown's avatar
      Fix for bug #22728 "Handler_rollback value is growing". · 0191c41f
      unknown authored
      The bug is present only in 4.1, will be null-merged to 5.0
      
      For InnoDB, check value of thd->transaction.all.innodb_active_trans instead of thd->transaction.stmt.innobase_tid to see if we really need to rollback.
      
      
      mysql-test/r/innodb_mysql.result:
        Added testcase for bug #22728 "Handler_rollback value is growing"
      mysql-test/t/innodb_mysql.test:
        Added testcase for bug #22728 "Handler_rollback value is growing"
      sql/handler.cc:
        For InnoDB, check value of thd->transaction.all.innodb_active_trans instead of thd->transaction.stmt.innobase_tid to see if we really need to rollback.
      0191c41f
    • unknown's avatar
      Merge naruto.:C:/cpp/bug21811/my41-bug21811 · 7d5bc1cb
      unknown authored
      into  naruto.:C:/cpp/mysql-4.1-maint
      
      
      sql/item_timefunc.cc:
        Auto merged
      7d5bc1cb
  6. 09 Oct, 2006 1 commit