1. 21 Aug, 2007 3 commits
  2. 20 Aug, 2007 1 commit
    • gshchepa/uchum@gleb.loc's avatar
      Fixed bug #30287. · 5d3809c2
      gshchepa/uchum@gleb.loc authored
      The server created temporary tables for filesort in the working directory
      instead of the specified tmpdir directory.
      5d3809c2
  3. 18 Aug, 2007 1 commit
  4. 17 Aug, 2007 1 commit
  5. 16 Aug, 2007 2 commits
  6. 15 Aug, 2007 8 commits
    • tsmith@ramayana.hindu.god's avatar
      NULL MERGE this ChangeSet to 5.1 · 5e926bc1
      tsmith@ramayana.hindu.god authored
      Apply innodb-5.0-ss1696 snapshot
      
      Fixes:
      - Bug#20090: InnoDB: Error: trying to declare trx to enter InnoDB
      - Bug#23710: crash_commit_before fails if innodb_file_per_table=1
        At InnoDB startup consider the case where log scan went beyond
        checkpoint_lsn as a crash and initiate crash recovery code path.
      - Bug#28781: InnoDB increments auto-increment value incorrectly with ON DUPLICATE KEY UPDATE
        We need to do some special AUTOINC handling for the following case:
        INSERT INTO t (c1,c2) VALUES(x,y) ON DUPLICATE KEY UPDATE ...
        We need to use the AUTOINC counter that was actually used by
        MySQL in the UPDATE statement, which can be different from the
        value used in the INSERT statement.
      - Bug#29097: fsp_get_available_space_in_free_extents() is capped at 4TB
        Fix by typecasting the variables before multiplying them, so that the
        result of the multiplication is of type "unsigned long long".
      - Bug#29155: Innodb "Parallel recovery" is not prevented
        Fix by enabling file locking on FreeBSD.  It has been disabled because
        InnoDB has refused to start on FreeBSD & LinuxThreads, but now it
        starts just fine.
      5e926bc1
    • tsmith@ramayana.hindu.god's avatar
      Merge ramayana.hindu.god:/home/tsmith/m/bk/50 · e2d64f28
      tsmith@ramayana.hindu.god authored
      into  ramayana.hindu.god:/home/tsmith/m/bk/maint/50
      e2d64f28
    • lars/lthalmann@dl145h.mysql.com's avatar
      Merge mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge · 04981779
      lars/lthalmann@dl145h.mysql.com authored
      into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
      04981779
    • lars/lthalmann@dl145k.mysql.com's avatar
      Merge mysql.com:/nfsdisk1/lars/bkroot/mysql-5.0-rpl · 4000c96a
      lars/lthalmann@dl145k.mysql.com authored
      into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge
      4000c96a
    • lars/lthalmann@mysql.com/dl145k.mysql.com's avatar
      Merge mysql.com:/nfsdisk1/lars/bkroot/mysql-4.1-rpl · 75925a19
      into  mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge
      75925a19
    • igor@olga.mysql.com's avatar
      Fixed bug #30396. · d790ec42
      igor@olga.mysql.com authored
      The bug caused memory corruption for some queries with top OR level
      in the WHERE condition if they contained equality predicates and 
      other sargable predicates in disjunctive parts of the condition.
      
      The corruption happened because the upper bound of the memory
      allocated for KEY_FIELD and SARGABLE_PARAM internal structures
      containing info about potential lookup keys was calculated incorrectly
      in some cases. In particular it was calculated incorrectly when the
      WHERE condition was an OR formula with disjuncts being AND formulas
      including equalities and other sargable predicates.
      d790ec42
    • evgen@moonbone.local's avatar
      mysql_client_test.c: · 222fddcb
      evgen@moonbone.local authored
        Post fix for the bug#29948.
      222fddcb
    • mhansson/martin@linux-st28.site's avatar
      bug#28570: handler::index_read() is called with different find_flag when · 1da8451d
      mhansson/martin@linux-st28.site authored
      ORDER BY is used
      
      The range analysis module did not correctly signal to the 
      handler that a range represents a ref (EQ_RANGE flag). This causes 
      non-range queries like 
      SELECT ... FROM ... WHERE keypart_1=const, ..., keypart_n=const 
      ORDER BY ... FOR UPDATE
      to wait for a lock unneccesarily if another running transaction uses
      SELECT ... FOR UPDATE on the same table.
      
      Fixed by setting EQ_RANGE for all range accesses that represent 
      an equality predicate. 
      1da8451d
  7. 14 Aug, 2007 3 commits
  8. 13 Aug, 2007 4 commits
  9. 10 Aug, 2007 1 commit
  10. 08 Aug, 2007 1 commit
  11. 07 Aug, 2007 4 commits
  12. 06 Aug, 2007 8 commits
  13. 05 Aug, 2007 3 commits
    • kent@mysql.com/kent-amd64.(none)'s avatar
      mysql-test-run.pl: · 6ab4112c
      kent@mysql.com/kent-amd64.(none) authored
        Search "relwithdebinfo" directory in CMake Visual Studio build
        Search for "mysqld-debug" even in source tree
      6ab4112c
    • igor@olga.mysql.com's avatar
      Merge olga.mysql.com:/home/igor/mysql-5.0-opt · a8debc65
      igor@olga.mysql.com authored
      into  olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug30219
      a8debc65
    • igor@olga.mysql.com's avatar
      Fix bug #30219. · 5f6df1b2
      igor@olga.mysql.com authored
      This bug manifested itself for queries with grouping by columns of
      the BIT type. It led to wrong comparisons of bit-field values and
      wrong result sets.
      Bit-field values never cannot be compared as binary values. Yet
      the class Field_bit had an implementation of the cmp method that
      compared bit-fields values as binary values. 
      Also the get_image and set_image methods of the base class Field 
      cannot be used for objects of the Field_bit class. 
      Now these methods are declared as virtual and specific implementations
      of the methods are provided for the class Field_bit.
      5f6df1b2