An error occurred fetching the project authors.
  1. 13 Oct, 2007 1 commit
    • aelkin/elkin@koti.dsl.inet.fi's avatar
      Bug #29136 erred multi-delete on trans table does not rollback the statement · ed0ab76e
      aelkin/elkin@koti.dsl.inet.fi authored
      similar to bug_27716, but it was stressed on in the synopsis on that there is another
      side of the artifact affecting behaviour in transaction.
      
      Fixed with deploying multi_delete::send_error() - otherwise never called - and refining its logic
      to perform binlogging job if needed.
      
      The changeset includes the following side effects:
      - added tests to check bug_23333's scenarios on the mixture of tables for multi_update;
      - fixes bug@30763 with two-liner patch and a test coinciding to one added for bug_23333.
      ed0ab76e
  2. 18 Jul, 2007 1 commit
  3. 19 Jun, 2007 1 commit
  4. 07 Jun, 2007 1 commit
  5. 01 Jun, 2007 1 commit
    • aelkin/elkin@dsl-hkibras1-ff5dc300-70.dhcp.inet.fi's avatar
      Bug #27716 multi-update did partially and has not binlogged · 1c0ac638
      Implementation of mysql_multi_update did not call multi_update::send_error method in some cases 
      (see the test reported on bug page and test cases in changeset).
      
      Fixed with deploying the method, ::send_error() is refined to get binlogging code which works whenever 
      there is modified non-transactional table.
      thd->no_trans_update.stmt flag is set in to TRUE to ease testing though being the beginning of relative 
      bug#27417 fix (addresses a part of those issues).
      Eliminating two minor issues (small bugs) in multi_update methods.
      This patch for multi-update also addresses a part of the issues reported in bug#13270,bug#23333.
      1c0ac638
  6. 19 Apr, 2007 1 commit
    • tsmith@siva.hindu.god's avatar
      Apply innodb-5.0-ss1405 snapshot · d232cead
      tsmith@siva.hindu.god authored
      NULL MERGE: this ChangeSet will be null merged into mysql-5.1
      
      Fixes:
      
      - Bug #26662: mysqld assertion when creating temporary (InnoDB) table on a tmpfs filesystem
        Fix by not open(2)ing with O_DIRECT but rather calling fcntl(2) to set
        this flag immediately after open(2)ing. This way an error caused by
        O_DIRECT not being supported can easily be ignored.
      - Bug #23313: AUTO_INCREMENT=# not reported back for InnoDB tables
      - Bug #21404: AUTO_INCREMENT value reset when Adding FKEY (or ALTER?)
        Report the current value of the AUTO_INCREMENT counter to MySQL.
      d232cead
  7. 22 Mar, 2007 1 commit
    • tsmith@siva.hindu.god's avatar
      NULL MERGE this to 5.1 · 8abc9536
      tsmith@siva.hindu.god authored
      Apply the following InnoDB snapshots:
      innodb-5.0-ss1319
      innodb-5.0-ss1331
      innodb-5.0-ss1333
      innodb-5.0-ss1341
      
      Fixes:
      - Bug #21409: Incorrect result returned when in READ-COMMITTED with query_cache ON
        At low transaction isolation levels we let each consistent read set
        its own snapshot.
      - Bug #23666: strange Innodb_row_lock_time_% values in show status; also millisecs wrong
        On Windows ut_usectime returns secs and usecs relative to the UNIX
        epoch (which is Jan, 1 1970).
      
      - Bug #25494: LATEST DEADLOCK INFORMATION is not always cleared
        lock_deadlock_recursive(): When the search depth or length is exceeded,
        rewind lock_latest_err_file and display the two transactions at the
        point of aborting the search.
      
      - Bug #25927: Foreign key with ON DELETE SET NULL on NOT NULL can crash server
        Prevent ALTER TABLE ... MODIFY ... NOT NULL on columns for which
        there is a foreign key constraint ON ... SET NULL.
      
      - Bug #26835: Repeatable corruption of utf8-enabled tables inside InnoDB
        The bug could be reproduced as follows:
      
        Define a table so that the first column of the clustered index is
        a VARCHAR or a UTF-8 CHAR in a collation where sequences of bytes
        of differing length are considered equivalent.
      
        Insert and delete a record.  Before the delete-marked record is
        purged, insert another record whose first column is of different
        length but equivalent to the first record.  Under certain conditions,
        the insertion can be incorrectly performed as update-in-place.
      
        Likewise, an operation that could be done as update-in-place can
        unnecessarily be performed as delete and insert, but that would not
        cause corruption but merely degraded performance.
      8abc9536
  8. 19 Feb, 2007 1 commit
    • kaa@polly.local's avatar
      Bug#18743: Several test cases fails if "classic" configuration in 5.0 · 315819fe
      kaa@polly.local authored
      The problem happened because those tests were using "cp932" and "ucs2" without checking whether these character sets are available. This fix moves test parts to make character set specific parts be tested only if they are:
      - some parts were moved to "ctype_ucs.test" and "ctype_cp932.test"
      - some parts were moved to the newly added tests "innodb-ucs2.test", "mysqlbinglog-cp932.test" and "sp-ucs2.test"
      315819fe
  9. 20 Nov, 2006 1 commit
    • monty@mysql.com/nosik.monty.fi's avatar
      Remove compiler warnings · e8258798
      monty@mysql.com/nosik.monty.fi authored
      (Mostly in DBUG_PRINT() and unused arguments)
      Fixed bug in query cache when used with traceing (--with-debug)
      Fixed memory leak in mysqldump
      Removed warnings from mysqltest scripts (replaced -- with #)
      e8258798
  10. 13 Nov, 2006 2 commits
  11. 21 Jul, 2006 1 commit
    • evgen@moonbone.local's avatar
      Fixed bug#12185: Data type aggregation may produce wrong result · c875b8eb
      evgen@moonbone.local authored
      The Item::tmp_table_field_from_field_type() function creates Field_datetime
      object instead of Field_timestamp object for timestamp field thus always
      changing data type is a tmp table is used.
      
      The Field_blob object constructor which is used in the 
      Item::tmp_table_field_from_field_type() is always setting packlength field of
      newly created blob to 4. This leads to changing fields data type for example
      from the blob to the longblob if a temporary table is used.
      
      The Item::make_string_field() function always converts Field_string objects 
      to Field_varstring objects. This leads to changing data type from the 
      char/binary to varchar/varbinary.
      
      Added appropriate Field_timestamp object constructor for using in the 
      Item::tmp_table_field_from_field_type() function.
      
      Added Field_blob object constructor which sets pack length according to
      max_length argument.
      
      The Item::tmp_table_field_from_field_type() function now creates
      Field_timestamp object for a timestamp field.
      
      The Item_type_holder::display_length() now returns correct NULL length NULL
      length. 
      
      The Item::make_string_field() function now doesn't change Field_string to
      Field_varstring in the case of Item_type_holder. 
      
      The Item::tmp_table_field_from_field_type() function now uses the Field_blob
      constructor which sets packlength according to max_length.
      c875b8eb
  12. 06 Jun, 2006 1 commit
  13. 03 May, 2006 1 commit
  14. 26 Apr, 2006 1 commit
  15. 20 Apr, 2006 2 commits
  16. 17 Apr, 2006 1 commit
  17. 12 Apr, 2006 1 commit
  18. 11 Apr, 2006 1 commit
  19. 29 Mar, 2006 2 commits
    • aivanov@mysql.com's avatar
      Restoring changes erroneously removed by applying · 6befdb5c
      aivanov@mysql.com authored
       the innodb-5.0-ss368 snapshot.
      6befdb5c
    • 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
  20. 24 Feb, 2006 1 commit
  21. 31 Jan, 2006 1 commit
  22. 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
  23. 18 Jan, 2006 1 commit
  24. 16 Jan, 2006 1 commit
    • aivanov@mysql.com's avatar
      Changes from the innodb-5.0-ss115 snapshot. · 708f9b3c
      aivanov@mysql.com authored
       Fixed bugs:
       BUG#15991: "innodb-file-per-table + symlink database + rename = crash"
       BUG#15650: "DELETE with LEFT JOIN crashes server"
       BUG#15308: "Problem of Order with Enum Column in Primary Key"
       BUG#14189: "VARBINARY and BINARY variables: trailing space ignored"
      708f9b3c
  25. 15 Jan, 2006 1 commit
  26. 13 Dec, 2005 1 commit
  27. 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
  28. 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
  29. 01 Dec, 2005 1 commit
  30. 19 Oct, 2005 1 commit
  31. 30 Sep, 2005 1 commit
    • serg@serg.mylan's avatar
      Bug#11238 · bef3c587
      serg@serg.mylan authored
      "SELECT ... FOR UPDATE executed as consistent read inside LOCK TABLES"
      Do not discard lock_type information as handler::start_stmt() may require knowledge.
      (fixed by Antony)
      bef3c587
  32. 29 Sep, 2005 2 commits
  33. 28 Sep, 2005 1 commit
  34. 23 Sep, 2005 2 commits
  35. 19 Sep, 2005 1 commit