- 23 Oct, 2008 1 commit
-
-
Mats Kindahl authored
-
- 21 Oct, 2008 1 commit
-
-
Kristofer Pettersson authored
Debug builds of MySQL 5.1, 6.0 with Sun Studio 12 broke because of use of gcc specific feature. The fix is to replace __FUNCTION__ with the corresponding character string
-
- 18 Oct, 2008 1 commit
-
-
Sven Sandberg authored
Problem 1: not_embedded_server runs SELECT FROM I_S.PROCESSLIST near the beginning. check_testcase executes a query to the server before that. There is a race here, because there is no guarantee that the thread executing check_testcase's query is finished. Problem 2: The SELECT FROM I_S.PROCESSLIST doens't seem very useful in the test. It's at least misplaced. Fix to both problems: Comment out SELECT FROM I_S.PROCESSLIST.
-
- 13 Oct, 2008 2 commits
-
-
Sven Sandberg authored
Problem: during a refactoring of mtr, a pattern for suppressing a warning from lowercase_table3 was lost. Fix: re-introduce the suppression. Problem 2: suppression was misspelt as supression. Fixed by adding a p.
-
Sven Sandberg authored
Post-push fixes making it work on pushbuild's valgrind host, and clarifying the output.
-
- 11 Oct, 2008 3 commits
-
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
- 10 Oct, 2008 3 commits
-
-
Magnus Svensson authored
BUG#39008 Additional fix after review, remove files that could potentially be set to path outside datadir
-
kent.boortz@sun.com authored
-
Magnus Svensson authored
-
- 09 Oct, 2008 4 commits
-
-
Gleb Shchepa authored
-
Gleb Shchepa authored
derived table cause crash When a multi-UPDATE command fails to lock some table, and subsequently succeeds, the tables need to be reopened if they were altered. But the reopening procedure failed for derived tables. Extra cleanup has been added.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
Fixed a compilation warning
-
- 08 Oct, 2008 19 commits
-
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
BUG#38559 Annoying cygwin problem fixed by resolving pid->winpid before kill instead of just after fork
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Magnus Svensson authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Ramil Kalimullin authored
upgrade from <=5.0.46 to >=5.0.48 Problem: 'check table .. for upgrade' doesn't detect incompatible collation changes made in 5.0.48. Fix: check for incompatible collation changes.
-
Mats Kindahl authored
-
Georgi Kodinov authored
-
Mats Kindahl authored
The failure was caused by executing a CREATE-SELECT statement that creates a table in another database than the current one. In row-based logging, the CREATE statement was written to the binary log without the database, hence creating the table in the wrong database, causing the following inserts to fail since the table didn't exist in the given database. Fixed the bug by adding a parameter to store_create_info() that will make the function print the database name before the table name and used that in the calls that write the CREATE statement to the binary log. The database name is only printed if it is different than the currently selected database. The output of SHOW CREATE TABLE has not changed and is still printed without the database name.
-
Georgi Kodinov authored
disabled a randomly failing test and opened a bug report
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Mattias Jonsson authored
InnoDB Plugin locks table This is a pre fix update that does the change to the handler api. This is done since there are already changes in this version, so the real fix does not need to change the api.
-
- 07 Oct, 2008 6 commits
-
-
Gleb Shchepa authored
-
Gleb Shchepa authored
``FLUSH TABLES WITH READ LOCK'' Concurrent execution of 1) multitable update with a NATURAL/USING join and 2) a such query as "FLUSH TABLES WITH READ LOCK" or "ALTER TABLE" of updating table led to a server crash. The mysql_multi_update_prepare() function call is optimized to lock updating tables only, so it postpones locking to the last, and if locking fails, it does cleanup of modified syntax structures and repeats a query analysis. However, that cleanup procedure was incomplete for NATURAL/USING join syntax data: 1) some Field_item items pointed into freed table structures, and 2) the TABLE_LIST::join_columns fields was not reset. Major change: short-living Field *Natural_join_column::table_field has been replaced with long-living Item*.
-
Georgi Kodinov authored
-
Gleb Shchepa authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-