1. 01 Apr, 2006 2 commits
  2. 30 Mar, 2006 16 commits
  3. 29 Mar, 2006 22 commits
    • monty@mysql.com's avatar
      Fix error in prefix compression of keys in MyISAM when key length changed from 254 -> 255 · 84e7c963
      monty@mysql.com authored
      Bug #17705 "FT Index corruption occurs with UTF8 data..."
      (Actually, the bug had nothing to do with FT index but with general key compression)
      84e7c963
    • kent@mysql.com's avatar
      mysql-test-run.pl: · 1f5ac05d
      kent@mysql.com authored
        Check that port range is valid, bug#16807
      1f5ac05d
    • kent@mysql.com's avatar
      mysqld_safe.sh: · 6ce9c90d
      kent@mysql.com authored
        Added --help option, bug#16392
      acinclude.m4:
        Use "$shrext_cmds" when testing if shared library exists, bug#16332
      6ce9c90d
    • kent@mysql.com's avatar
      Makefile.am: · 3a0d957f
      kent@mysql.com authored
        Use "dist_bin_SCRIPTS" to get a script distributed
      3a0d957f
    • kent@mysql.com's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-4.1 · 572677b9
      kent@mysql.com authored
      into mysql.com:/Users/kent/mysql/bk/mysql-4.1-new
      572677b9
    • kent@mysql.com's avatar
      Makefile.am: · a0a4381e
      kent@mysql.com authored
        Use "dist_bin_SCRIPTS" to get a script distributed
      a0a4381e
    • bpontz@mysql.com's avatar
      configure.in: · c1ac02a4
      bpontz@mysql.com authored
        Increased version number because of clone-off
      c1ac02a4
    • konstantin@mysql.com's avatar
      d360687d
    • konstantin@mysql.com's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 38bd424a
      konstantin@mysql.com authored
      into  mysql.com:/opt/local/work/mysql-5.0-15683
      38bd424a
    • aivanov@mysql.com's avatar
      Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-5.0 · 2dfb139c
      aivanov@mysql.com authored
      into  mysql.com:/home/alexi/innodb/mysql-5.0-merge
      2dfb139c
    • aivanov@mysql.com's avatar
      Restoring changes erroneously removed by applying · 6befdb5c
      aivanov@mysql.com authored
       the innodb-5.0-ss368 snapshot.
      6befdb5c
    • evgen@moonbone.local's avatar
      Fixed bug#15560: GROUP_CONCAT wasn't ready for WITH ROLLUP queries · 1c13e548
      evgen@moonbone.local authored
      The GROUP_CONCAT uses its own temporary table. When ROLLUP is present
      it creates the second copy of Item_func_group_concat. This copy receives the
      same list of arguments that original group_concat does. When the copy is
      set up the result_fields of functions from the argument list are reset to the
      temporary table of this copy.
      As a result of this action data from functions flow directly to the ROLLUP copy
      and the original group_concat functions shows wrong result.
      Since queries with COUNT(DISTINCT ...) use temporary tables to store
      the results the COUNT function they are also affected by this bug.
      
      The idea of the fix is to copy content of the result_field for the function
      under GROUP_CONCAT/COUNT from  the first temporary table to the second one,
      rather than setting result_field to point to the second temporary table.
      To achieve this goal force_copy_fields flag is added to Item_func_group_concat
      and Item_sum_count_distinct classes. This flag is initialized to 0 and set to 1
      into the make_unique() member function of both classes.
      To the TMP_TABLE_PARAM structure is modified to include the similar flag as
      well.
      The create_tmp_table() function passes that flag to create_tmp_field().
      When the flag is set the create_tmp_field() function will set result_field
      as a source field and will not reset that result field to newly created 
      field for Item_func_result_field and its descendants. Due to this there
      will be created copy func to copy data from old result_field to newly 
      created field.
      1c13e548
    • aivanov@mysql.com's avatar
      Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-5.0 · 32068206
      aivanov@mysql.com authored
      into  mysql.com:/home/alexi/innodb/mysql-5.0-merge
      32068206
    • aivanov@mysql.com's avatar
      Applied innodb-5.0-ss368 snapshot · 99d17803
      aivanov@mysql.com authored
        Fixed bugs:
        #16814: SHOW INNODB STATUS format error in LATEST FOREIGN KEY ERROR section
          dict_foreign_key_error_report(): Always print a newline after invoking
          dict_print_info_on_foreign_key_in_create_format().
        #16827: Better InnoDB error message if ibdata files omitted from my.cnf.
        #17126: CHECK TABLE on InnoDB causes a short hang during check of adaptive hash.
          CHECK TABLE blocking other queries, by releasing the btr_search_latch
          periodically during the adaptive hash table validation.
        #17405: Valgrind: conditional jump or move depends on uninitialised valuesw.
          buf_block_init(): Reset magic_n, buf_fix_count, and io_fix to avoid testing
          uninitialised variables.
        #18077: InnoDB uses full explicit table locks in stored FUNCTION.
        #18238: When locks exhaust the buffer pool, InnoDB does not roll back the trx.
          Check in pessimistic insert and update if the buffer pool is exhausted by locks.
        #18252: Disk space leaks in updates of InnoDB BLOB rows.
          btr_cur_pessimistic_update(): Invoke rec_get_offset() after rec_set_field_extern_bits().
          btr_store_big_rec_extern_fields(): Note that offsets will no longer be valid
          after calling this function.
        #18283: When InnoDB returns error 'lock table full', MySQL can write to binlog too much.
        #18384: InnoDB memory leak on duplicate key errors if row has many columns.
          row_ins_duplicate_error_in_clust(): Call mem_heap_free(heap) at func_exit if needed.
        #18350: Use consistent read in CREATE ... SELECT .. if innodb_locks_unsafe_for_binlog is used.
      99d17803
    • cmiller@zippy.(none)'s avatar
      c07a84f7
    • gluh@mysql.com's avatar
      Merge sgluhov@bk-internal.mysql.com:/home/bk/mysql-4.1 · a87c8008
      gluh@mysql.com authored
      into mysql.com:/home/gluh/MySQL/Merge/4.1
      a87c8008
    • gluh@eagle.intranet.mysql.r18.ru's avatar
      Fix for bug#15316 SET value having comma not correctly handled · 2545c7d4
      gluh@eagle.intranet.mysql.r18.ru authored
       disallow the use of comma in SET members
      2545c7d4
    • bar@mysql.com's avatar
      Additional 5.0 fix for · 07e21be0
      bar@mysql.com authored
      Bug#15098: CAST(column double TO signed int), wrong result
      which was fixed originally in 4.1.
      07e21be0
    • kent@mysql.com's avatar
      Merge · 0d332aef
      kent@mysql.com authored
      0d332aef
    • kent@mysql.com's avatar
      mysql_config.sh: · 67f2b0f3
      kent@mysql.com authored
        If installed, search built in lib path first, bug#13158
      67f2b0f3
    • kent@mysql.com's avatar
      Makefile.am: · 37b916a7
      kent@mysql.com authored
        Added "ndb_error_reporter" script, bug#18421
      37b916a7
    • kent@mysql.com's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-4.1 · ca29e362
      kent@mysql.com authored
      into mysql.com:/Users/kent/mysql/bk/mysql-4.1-new
      ca29e362