An error occurred fetching the project authors.
  1. 19 Dec, 2006 1 commit
    • tsmith/tim@siva.hindu.god's avatar
      This ChangeSet must be null-merged to 5.1. · d60550a4
      tsmith/tim@siva.hindu.god authored
      Applied innodb-5.0-ss1040 and innodb-5.0-ss1099 snapshots.
      
      Bugs fixed:
      - Bug #21468: InnoDB crash during recovery with corrupted data pages: XA bug?
      - Bug #24299: Identifiers in foreign keys cannot contain U+0160, U+0360, ..., U+FF60
      - Bug #24386: Performance degradation caused by instrumentation in mutex_struct
      - Bug #24712: SHOW TABLE STATUS for file-per-table showing incorrect time fields
      d60550a4
  2. 18 Aug, 2006 1 commit
  3. 20 Apr, 2006 2 commits
    • aivanov@mysql.com's avatar
      Applied innodb-5.0-ss476 snapshot. · 25d9a75d
      aivanov@mysql.com authored
       Fix BUG#18934: "InnoDB crashes when table uses column like DB_ROW_ID".
       Also, fix memory leaks in row_create_table_for_mysql() in rare
       corner cases.
      25d9a75d
    • aivanov@mysql.com's avatar
      Applied innodb-4.1-ss22 snapshot. · b7583537
      aivanov@mysql.com authored
       Fix BUG#16814: "SHOW INNODB STATUS format error in LATEST FOREIGN KEY ERROR section"
           Add a missing newline to the LAST FOREIGN KEY ERROR section in SHOW INNODB STATUS
           output.
       Fix BUG#18934: "InnoDB crashes when table uses column names like DB_ROW_ID".
           Refuse tables that use reserved column names.
      b7583537
  4. 29 Mar, 2006 1 commit
    • 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
  5. 31 Jan, 2006 1 commit
  6. 30 Jan, 2006 1 commit
    • aivanov@mysql.com's avatar
      Fixed BUG#16387. · fe518520
      aivanov@mysql.com authored
        Applied innodb-4.1-ss17 snapshot.
        Do not mistake TABLENAME_ibfk_0 for auto-generated id.
      fe518520
  7. 12 Dec, 2005 1 commit
    • aivanov@mysql.com's avatar
      Fix BUG#12071: "Windows hang: 'Opening tables' or 'Waiting for · 7ae2d469
      aivanov@mysql.com authored
       table' lockup".
       Changes from the innodb-4.1-ss11 snapshot.
       Do not call os_file-create_tmpfile() at runtime. Instead, create
       a tempfile at startup and guard access to it with a mutex.
       Also, fix bugs:
       10511: "Wrong padding of UCS2 CHAR columns in ON UPDATE CASCADE";
       13778: "If FOREIGN_KEY_CHECKS=0, one can create inconsistent FOREIGN
       KEYs". When FOREIGN_KEY_CHECKS=0 we still need to check that
       datatypes between foreign key references are compatible.
       Also, added test cases (also for bug 9802).
      7ae2d469
  8. 06 Dec, 2005 1 commit
    • aivanov@mysql.com's avatar
      Fix BUG#14747: "Race condition can cause btr_search_drop_page_hash_index() · 9eee2547
      aivanov@mysql.com authored
       to crash".
       Changes from snapshot innodb-5.0-ss52.
       Note that buf_block_t::index should be protected by btr_search_latch
       or an s-latch or x-latch on the index page.
       btr_search_drop_page_hash_index(): Read block->index while holding
       btr_search_latch and use the cached value in the loop. Remove some
       redundant assertions.
       Also fix 13778. When FOREIGN_KEY_CHECKS=0 we still need to check that
       datatypes between foreign key references are compatible.
       Also added test cases to 9802.
      9eee2547
  9. 23 Sep, 2005 2 commits
  10. 06 Sep, 2005 1 commit
  11. 26 Apr, 2005 1 commit
    • heikki@hundin.mysql.fi's avatar
      dict0dict.c, dict0dict.h, fil0fil.c: · bea92e16
      heikki@hundin.mysql.fi authored
        Fix a problem in crash recovery of .ibd files on Windows if the user used lower_case_table_names=0 or 2; the directory scan in crash recovery forgot to put all paths to lower case, so that the tablespace name would be consistent with the internal data dictionary of InnoDB; remember that InnoDB puts internally all database names and table names to lower case on Windows, regardless of the value of lower_case_table_names
      bea92e16
  12. 22 Apr, 2005 1 commit
    • marko@hundin.mysql.fi's avatar
      dict0dict.c: · d7f9dffd
      marko@hundin.mysql.fi authored
        Add some UNIV_LIKELY and UNIV_UNLIKELY hints.
        dict_tree_copy_rec_order_prefix(): Add a UNIV_PREFETCH_R hint on rec.
      d7f9dffd
  13. 12 Apr, 2005 1 commit
  14. 05 Apr, 2005 1 commit
    • heikki@hundin.mysql.fi's avatar
      dict0dict.c: · 9db39659
      heikki@hundin.mysql.fi authored
        Add a note that ENUM in new tables cannot reference ENUM in old tables, in FOREIGN KEY constraints
      9db39659
  15. 07 Mar, 2005 1 commit
  16. 28 Feb, 2005 1 commit
  17. 25 Feb, 2005 1 commit
  18. 04 Feb, 2005 1 commit
  19. 21 Jan, 2005 1 commit
    • heikki@hundin.mysql.fi's avatar
      dict0dict.c: · 9a03676b
      heikki@hundin.mysql.fi authored
        Fix bug #7831: ALTER TABLE ... ADD CONSTRAINT PRIMARY KEY ... complained about bad foreign key definition
      9a03676b
  20. 14 Jan, 2005 1 commit
  21. 29 Dec, 2004 1 commit
  22. 10 Dec, 2004 4 commits
    • heikki@hundin.mysql.fi's avatar
      dict0dict.c, log.cc: · 713a3103
      heikki@hundin.mysql.fi authored
        Remove accidentally merged 4.0 changes
      dict0dict.c:
        Remove the 4.0 fix accidentally auto-merged to 4.1
      row0mysql.h, dict0dict.h:
        Remove a change auto-merged from 4.0
      713a3103
    • heikki@hundin.mysql.fi's avatar
      dict0dict.h, dict0dict.c, ha_innodb.cc: · ea6b5e11
      heikki@hundin.mysql.fi authored
        Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
      ea6b5e11
    • heikki@hundin.mysql.fi's avatar
      dict0dict.c: · 536702f4
      heikki@hundin.mysql.fi authored
        In the FOREIGN KEY parser, do not cut 0xC2A0 from the end of an identifier if it was quoted
      536702f4
    • heikki@hundin.mysql.fi's avatar
      dict0dict.c: · 4915d196
      heikki@hundin.mysql.fi authored
        Fix the bug that the character 0xA0 that EMS MySQL Manager in ALTER TABLE adds after a table name confuses the InnoDB FOREIGN KEY parser, causing an error 121 when we try to add a new constraint; a full fix would require the lexer to be aware of thd->charset_info() and UTF-8
      4915d196
  23. 02 Dec, 2004 1 commit
    • marko@hundin.mysql.fi's avatar
      Many files: · dd489539
      marko@hundin.mysql.fi authored
        Implement more compact InnoDB record format.
        Old format is available as CREATE TABLE ... ROW_FORMAT=DYNAMIC.
      dd489539
  24. 03 Nov, 2004 1 commit
  25. 31 Oct, 2004 1 commit
    • heikki@hundin.mysql.fi's avatar
      row0mysql.c, pars0pars.c, eval0eval.c, dict0load.c, dict0dict.c, dict0crea.c: · d22a24d8
      heikki@hundin.mysql.fi authored
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it
      dict0dict.c:
        Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it; fix also a hang that would occur if one tried in ALTER TABLE or RENAME TABLE to create a foreign key constraint name that collided with another existing name
      d22a24d8
  26. 18 Oct, 2004 1 commit
  27. 14 Oct, 2004 1 commit
  28. 07 Oct, 2004 1 commit
    • heikki@hundin.mysql.fi's avatar
      Many files: · 89ecfd7f
      heikki@hundin.mysql.fi authored
        Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
      89ecfd7f
  29. 04 Oct, 2004 1 commit
  30. 01 Oct, 2004 1 commit
  31. 16 Sep, 2004 1 commit
  32. 10 Sep, 2004 1 commit
  33. 08 Sep, 2004 1 commit
  34. 06 Aug, 2004 1 commit
  35. 17 Jun, 2004 1 commit