1. 27 Oct, 2006 1 commit
    • unknown's avatar
      Fix for bug #23412: delete rows with null date field · d2718abe
      unknown authored
      Backport of the fix for bug #8143: A date with value 0 is treated as a NULL value
      
      
      mysql-test/r/delete.result:
        Fix for bug #23412: delete rows with null date field
          - test result
      mysql-test/t/delete.test:
        Fix for bug #23412: delete rows with null date field
          - test case
      sql/sql_delete.cc:
        Fix for bug #23412: delete rows with null date field
          - during SELECT queries processing we convert 'date[time]_field is null'                   
            conditions into 'date[time]_field = 0000-00-00[ 00:00:00]' for not null                  
            DATE and DATETIME fields. To be consistent, we have to do the same for DELETE            
            queries. So we should call remove_eq_conds() in the mysql_delete() as well.              
            Also it may simplify and speed up DELETE queries execution.
      d2718abe
  2. 25 Oct, 2006 4 commits
  3. 24 Oct, 2006 8 commits
  4. 23 Oct, 2006 9 commits
  5. 20 Oct, 2006 4 commits
  6. 19 Oct, 2006 10 commits
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.1-maint · e2dc947d
      unknown authored
      into  neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
      
      e2dc947d
    • unknown's avatar
      Adapt to running from "binary dist" · dd255ae5
      unknown authored
      Add function mtr_exe_maybe_exists to look for binaries that is optional
      Skip ndb support if it's a binary dist where mysqld supports ndb but there is no ndbd
      
      
      mysql-test/lib/mtr_misc.pl:
        Add function mtr_exe_maybe_exists
      mysql-test/mysql-test-run.pl:
        Adapt to running from binary dist
        Add function mtr_exe_maybe_exists to look for binaries that is optional
        Skip ndb support if it's a binary dist where mysqld supports ndb but there is no ndbd
      dd255ae5
    • unknown's avatar
      Fix problem running rpl_timezone on powermacg5, it was not popular to set TZ to "" so now it's set · e9d48045
      unknown authored
      to a value wich is not our default
      
      e9d48045
    • unknown's avatar
      Add command "exit" to mysqltest, it will stop processing any more · 1def5fee
      unknown authored
      commands and go directly to result file processing
      
      
      client/mysqltest.c:
        Add command "exit" to mysqltest
      mysql-test/r/mysqltest.result:
        Add command "exit" to mysqltest
      mysql-test/t/mysqltest.test:
        Add command "exit" to mysqltest
      1def5fee
    • unknown's avatar
      Merge ahristov@bk-internal.mysql.com:/home/bk/mysql-4.1-maint · f3a262a8
      unknown authored
      into  example.com:/work/bug23379/my41-bug23379
      
      
      sql/sql_class.cc:
        Auto merged
      f3a262a8
    • unknown's avatar
      Fix for bug#23379 "wrong time value in SHOW PROCESSLIST" · f042e23b
      unknown authored
        
      The value taken to be shown in SHOW PROCESSLIST is not
      initialized when THD is created and will be random for
      unauthenticated connections.
        
      To the documentor: Random value, instead of NULL, was shown,
      in SHOW PROCESSLIST for still non-authenticated connections.
      
      
      sql/sql_class.cc:
        Initialize time_after_lock.
        It is used from SHOW PROCESSLIST's code. If not initialized
        random value is shown for connected but still unauthenticated
        clients in the column Time.
      f042e23b
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.1-maint · a3f16fe8
      unknown authored
      into  neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
      
      a3f16fe8
    • unknown's avatar
      Backport test cases fixes from 5.0 · 0093ed34
      unknown authored
      
      client/mysqldump.c:
        fflush stderr after printing of error message
      mysql-test/include/have_lowercase0.inc:
        Remove extra ;
      mysql-test/r/rpl000015.result:
        Update result
      mysql-test/r/rpl_change_master.result:
        Update result
      mysql-test/r/rpl_error_ignored_table.result:
        Update result
      mysql-test/r/rpl_loaddata.result:
        Update result
      mysql-test/r/rpl_log.result:
        Update result
      mysql-test/r/rpl_max_relay_size.result:
        Update result
      mysql-test/r/rpl_replicate_do.result:
        Update result
      mysql-test/t/lowercase_table3.test:
        Backport from 5.0
      mysql-test/t/mysql_protocols.test:
        Backport from 5.0
      mysql-test/t/rpl000015.test:
        Backport from 5.0
      mysql-test/t/rpl_change_master.test:
        Backport from 5.0
      mysql-test/t/rpl_drop_db.test:
        Backport from 5.0
      mysql-test/t/rpl_error_ignored_table.test:
        Backport from 5.0
      mysql-test/t/rpl_loaddata.test:
        Backport from 5.0
      mysql-test/t/rpl_log-master.opt:
        Use --force-restart command in master.opt to force a restart for this test case
      mysql-test/t/rpl_log.test:
        Backport from 5.0
      mysql-test/t/rpl_max_relay_size.test:
        Backport from 5.0
      mysql-test/t/rpl_replicate_do.test:
        Backport from 5.0
      0093ed34
    • unknown's avatar
      Merge ahristov@bk-internal.mysql.com:/home/bk/mysql-4.1-maint · 0fb45b42
      unknown authored
      into  example.com:/work/bug23379/my41-bug23379
      
      0fb45b42
    • 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
  7. 18 Oct, 2006 4 commits