Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Bug#31210: INSERT DELAYED crashes server when used on partitioned tables | Mattias Jonsson | 2008-06-03 | 1 | -2/+2 |
| | | | | | | | | | | | Problem was an unclear error message since it could suggest that MyISAM did not support INSERT DELAYED. Changed the error message to say that DELAYED is not supported by the table, instead of the table's storage engine. The confusion is that a partitioned table is in somewhat sense using the partitioning storage engine, which in turn uses the ordinary storage engine. By saying that the table does not support DELAYED we do not give any extra informantion about the storage engine or if it is partitioned. | ||||
* | Fix for BUG#25507 "multi-row insert delayed + auto increment causes | guilhem@gbichot3.local | 2007-02-15 | 1 | -2/+2 |
| | | | | | | | | | | | | | | duplicate key entries on slave" (two concurrrent connections doing multi-row INSERT DELAYED to insert into an auto_increment column, caused replication slave to stop with "duplicate key error" (and binlog was wrong)), and BUG#26116 "If multi-row INSERT DELAYED has errors, statement-based binlogging breaks" (the binlog was not accounting for all rows inserted, or slave could stop). The fix is that: if (statement-based) binlogging is on, a multi-row INSERT DELAYED is silently converted to a non-delayed INSERT. Note: it is not possible to test BUG#25507 in 5.0 (requires mysqlslap), so it is tested only in the changeset for 5.1. However, BUG#26116 is tested here, and the fix for BUG#25507 is the same code change. | ||||
* | Added end marker for tests to make future merges easier | monty@mysql.com | 2005-07-28 | 1 | -0/+1 |
| | |||||
* | Small fixes done while reviewing pushed code | monty@mysql.com | 2005-04-06 | 1 | -0/+4 |
| | |||||
* | Clean up InnoDB testing with embedded server. | jimw@mysql.com | 2005-03-29 | 1 | -0/+17 |