1. 24 Apr, 2007 1 commit
  2. 17 Apr, 2007 2 commits
    • unknown's avatar
      Merge siva.hindu.god:/home/tsmith/m/bk/41 · 4e387d6c
      unknown authored
      into  siva.hindu.god:/home/tsmith/m/bk/maint/41
      
      
      4e387d6c
    • unknown's avatar
      Fix for bug #27515: DROP previlege is not required anymore for RENAME TABLE · 50e15840
      unknown authored
      Added missed DROP privilege check on the original table for RENAME TABLE command.
      
      
      mysql-test/r/grant.result:
        Fix for bug #27515: DROP previlege is not required anymore for RENAME TABLE
          - test result.
      mysql-test/t/grant.test:
        Fix for bug #27515: DROP previlege is not required anymore for RENAME TABLE
          - test case.
      sql/sql_parse.cc:
        Fix for bug #27515: DROP previlege is not required anymore for RENAME TABLE
          - added DROP privilege check on the original table for RENAME TABLE command.
      50e15840
  3. 14 Apr, 2007 1 commit
  4. 12 Apr, 2007 1 commit
  5. 11 Apr, 2007 4 commits
  6. 10 Apr, 2007 8 commits
  7. 07 Apr, 2007 2 commits
  8. 05 Apr, 2007 3 commits
    • unknown's avatar
      Add "query_sorted" command to mysqltest · e3e600bc
      unknown authored
      Usage:
        query_sorted <query>;
      
      
      client/mysqltest.c:
        Add query_sorted command to mysqltest
      mysql-test/r/mysqltest.result:
        Update result
      mysql-test/t/mysqltest.test:
        Add tests for query_sorted
      e3e600bc
    • unknown's avatar
      Protect against dying twice · 390a0ede
      unknown authored
      Cleanup exit handling
      
      
      390a0ede
    • unknown's avatar
      Deleted reject files accidently checked in · f76ab0c4
      unknown authored
        configure.in.rej
        include/my_global.h.rej
        BUILD/SETUP.sh.rej
        mysys/thr_alarm.c.rej
        include/my_pthread.h.rej
      
      
      BitKeeper/deleted/.del-SETUP.sh.rej:
        Delete: BUILD/SETUP.sh.rej
      BitKeeper/deleted/.del-configure.in.rej:
        Delete: configure.in.rej
      BitKeeper/deleted/.del-my_global.h.rej:
        Delete: include/my_global.h.rej
      BitKeeper/deleted/.del-my_pthread.h.rej:
        Delete: include/my_pthread.h.rej
      BitKeeper/deleted/.del-thr_alarm.c.rej:
        Delete: mysys/thr_alarm.c.rej
      f76ab0c4
  9. 04 Apr, 2007 4 commits
  10. 03 Apr, 2007 1 commit
    • unknown's avatar
      Fixed bug #27532: wrong results with ORDER/GROUP BY queries containing · 0ee34b1c
      unknown authored
      IN/BETWEEN predicates in sorting expressions.
      Wrong results may occur when the select list contains an expression
      with IN/BETWEEN predicate that differs from a sorting expression by
      an additional NOT only.
       
      Added the method Item_func_opt_neg::eq to compare correctly expressions
      containing [NOT] IN/BETWEEN.
      The eq method inherited from the Item_func returns TRUE when comparing
      'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.  
      
      
      mysql-test/r/order_by.result:
        Added a test case for bug #27532.
      mysql-test/t/order_by.test:
        Added a test case for bug #27532.
      sql/item_cmpfunc.cc:
        Fixed bug #27532.
        Added the method Item_func_opt_neg::eq to compare correctly expressions
        containing [NOT] IN/BETWEEN.
        The eq method inherited from the Item_func returns TRUE when comparing
        'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.
      sql/item_cmpfunc.h:
        Added the method Item_func_opt_neg::eq to compare correctly expressions
        containing [NOT] IN/BETWEEN.
        The eq method inherited from the Item_func returns TRUE when comparing
        'a IN (1,2)' with 'a NOT IN (1,2)' that is not, of course, correct.
      0ee34b1c
  11. 02 Apr, 2007 2 commits
  12. 31 Mar, 2007 1 commit
  13. 30 Mar, 2007 2 commits
    • unknown's avatar
      BUG#26624: high mem usage (crash) in range optimizer · 080c0c7a
      unknown authored
      Pushbuild fixes: 
       - Make MAX_SEL_ARGS smaller (even 16K records_in_range() calls is 
         more than it makes sense to do in typical cases)
       - Don't call sel_arg->test_use_count() if we've already allocated 
         more than MAX_SEL_ARGs elements. The test will succeed but will take
         too much time for the test suite (and not provide much value).
      
      
      mysql-test/r/range.result:
        BUG#26624: high mem usage (crash) in range optimizer
        Pushbuild fixes: make the test go faster
      mysql-test/t/range.test:
        BUG#26624: high mem usage (crash) in range optimizer
        Pushbuild fixes: make the test go faster
      080c0c7a
    • unknown's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-4.1 · ade8bbf4
      unknown authored
      into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build
      
      
      ade8bbf4
  14. 29 Mar, 2007 4 commits
  15. 28 Mar, 2007 4 commits
    • unknown's avatar
      Bug #26642: create index corrupts table definition in .frm · 0b72b7f0
      unknown authored
      Thanks to Martin Friebe for finding and submitting a fix for this bug!
      
      A table with maximum number of key segments and maximum length key name
      would have a corrupted .frm file, due to an incorrect calculation of the
      complete key length.  Now the key length is computed correctly (I hope) :-)
      
      MyISAM would reject a table with the maximum number of keys and the maximum
      number of key segments in all keys.  It would allow one less than this total
      maximum.  Now MyISAM accepts a table defined with the maximum.  (This is a
      very minor issue.)
      
      
      myisam/mi_open.c:
        change >= to > in a comparison (i.e., error only if key_parts_in_table
        really is greater than MAX_KEY * MAX_KEY_SEG)
      mysql-test/r/create.result:
        Add test results for bug #26642 (create index corrupts table definition in .frm)
      mysql-test/t/create.test:
        Add test case for bug #26642 (create index corrupts table definition in .frm)
      sql/table.cc:
        In create_frm(), fix formula for key_length; it was too small by (keys * 2) bytes
      0b72b7f0
    • unknown's avatar
      Merge mysql.com:/home/psergey/mysql-4.1-bug26625 · edd5a859
      unknown authored
      into  mysql.com:/home/psergey/mysql-4.1-bug26624-r2
      
      
      edd5a859
    • unknown's avatar
      BUG#26624: high mem usage (crash) in range optimizer · 9639eb3d
      unknown authored
      - Added PARAM::alloced_sel_args where we count the # of SEL_ARGs
        created by SEL_ARG tree cloning operations.
      - Made the range analyzer to shortcut and not do any more cloning 
        if we've already created MAX_SEL_ARGS SEL_ARG objects in cloning.
      - Added comments about space complexity of SEL_ARG-graph 
        representation.
      
      
      mysql-test/r/range.result:
        BUG#26624: Testcase
      mysql-test/t/range.test:
        BUG#26624: Testcase
      9639eb3d
    • unknown's avatar
      Delete: sql/mysqld.cc.rej · 60189d35
      unknown authored
      60189d35