An error occurred fetching the project authors.
- 13 Oct, 2007 1 commit
-
-
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.
-
- 18 Jul, 2007 1 commit
-
-
kostja@bodhi.(none) authored
Fix the typo in the constructor. Cover a semantic check that previously never worked with a test.
-
- 19 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
- Move binlog related tests to binlog_innodb.test - Remove "source include/have_log_bin.inc" from innodb.test
-
- 07 Jun, 2007 1 commit
-
-
msvensson@pilot.(none) authored
- Turn on binlog only for tests that need it - Skip those tests if --skip-binlog is used
-
- 01 Jun, 2007 1 commit
-
-
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.
-
- 19 Apr, 2007 1 commit
-
-
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.
-
- 22 Mar, 2007 1 commit
-
-
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.
-
- 19 Feb, 2007 1 commit
-
-
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"
-
- 20 Nov, 2006 1 commit
-
-
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 #)
-
- 13 Nov, 2006 2 commits
-
-
holyfoot/hf@mysql.com/deer.(none) authored
-
holyfoot/hf@mysql.com/deer.(none) authored
-
- 21 Jul, 2006 1 commit
-
-
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.
-
- 06 Jun, 2006 1 commit
-
-
aivanov@mysql.com authored
Fixed BUG#19727 "InnoDB crashed server and crashed tables are not recoverable".
-
- 03 May, 2006 1 commit
-
-
holyfoot@deer.(none) authored
-
- 26 Apr, 2006 1 commit
-
-
aivanov@mysql.com authored
Use files innodb_mysql.[test|result] instead.
-
- 20 Apr, 2006 2 commits
-
-
aivanov@mysql.com authored
the innodb-5.0-ss476 snapshot.
-
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.
-
- 17 Apr, 2006 1 commit
-
-
gkodinov@mysql.com authored
Testsuite added
-
- 12 Apr, 2006 1 commit
-
-
holyfoot@deer.(none) authored
-
- 11 Apr, 2006 1 commit
-
-
ramil@mysql.com authored
-
- 29 Mar, 2006 2 commits
-
-
aivanov@mysql.com authored
the innodb-5.0-ss368 snapshot.
-
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.
-
- 24 Feb, 2006 1 commit
-
-
monty@mysql.com authored
(Needed for "list of pushes" web page and autopush)
-
- 31 Jan, 2006 1 commit
-
-
aivanov@mysql.com authored
Applied innodb-5.0-ss149/162 snapshots.
-
- 30 Jan, 2006 1 commit
-
-
aivanov@mysql.com authored
Applied innodb-4.1-ss17 snapshot. Do not mistake TABLENAME_ibfk_0 for auto-generated id.
-
- 18 Jan, 2006 1 commit
-
-
aivanov@mysql.com authored
Make innodb_thread_concurrency 0 by default, and extend the usable range from 0 to 1000 (0 disables the thread throttling).
-
- 16 Jan, 2006 1 commit
-
-
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"
-
- 15 Jan, 2006 1 commit
-
-
aivanov@mysql.com authored
Fixed BUG#14056: Column prefix index on UTF-8 primary key causes "Can't find record.." Also fixed bug 15991.
-
- 13 Dec, 2005 1 commit
-
-
aivanov@mysql.com authored
table' lockup". Changes from the innodb-5.0-ss92 snapshot. Do not call os_file_create_tmpfile() at runtime. Instead, create all tempfiles at startup and guard access to them with mutexes.
-
- 12 Dec, 2005 1 commit
-
-
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).
-
- 06 Dec, 2005 1 commit
-
-
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.
-
- 01 Dec, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 19 Oct, 2005 1 commit
-
-
elliot@mysql.com authored
Applying InnoDB patch from Jan Lindstrom
-
- 30 Sep, 2005 1 commit
-
-
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)
-
- 29 Sep, 2005 2 commits
-
-
jan@hundin.mysql.fi authored
i.e. range test.
-
jan@hundin.mysql.fi authored
consistent read (Bug #12669). This fixes InnoDB part of the bug.
-
- 28 Sep, 2005 1 commit
-
-
jan@hundin.mysql.fi authored
consistent read (Bug #12669).
-
- 23 Sep, 2005 2 commits
-
-
osku@127.(none) authored
-
osku@127.(none) authored
-
- 19 Sep, 2005 1 commit
-
-
evgen@moonbone.local authored
This is backport from 5.0 of fix for bug #11039
-