- 12 Feb, 2009 1 commit
-
-
Chad MILLER authored
-
- 11 Feb, 2009 5 commits
-
-
Luis Soares authored
The test case relies on binlog entries for assertion. The problem is that the binlog does not get cleaned in pushbuild between tests, resulting in extra entries in the result file, causing the test to fail. This fix adds a reset master at the beginning of the test, so that we get a clean binlog file.
-
Horst Hunger authored
-
Luis Soares authored
-
Vladislav Vaintroub authored
-
Horst Hunger authored
Reviewed fix for bug#40882: Replaced "sleep 1" by wait_condition, added save/restore start values and closed open sessions. When trying to use "wait_for_query_to_succeed" a type has been fixed, also in "rename.test": Added session count and check and replaced error numbers.
-
- 10 Feb, 2009 12 commits
-
-
Mats Kindahl authored
-
Mats Kindahl authored
TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported. Correcting some tests that was failing in pushbuild as well as fixing result file for some tests that are not executed in the default MTR run.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Mats Kindahl authored
-
Chad MILLER authored
-
Mats Kindahl authored
Post-merge fixes. Changes to some result sets.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
based on NetBSD CVS as of 2009/02/06 20:09:00.
-
Vladislav Vaintroub authored
-
Luis Soares authored
There is an inconsistency with DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS and DROP VIEW IF EXISTS: those are binlogged even if the DB or TABLE does not exist, whereas DROP PROCEDURE IF EXISTS does not. It would be nice or at least consistent if DROP PROCEDURE/STATEMENT worked the same too. Fixed DROP PROCEDURE|FUNCTION IF EXISTS by adding a call to write_bin_log in mysql_execute_command. Checked also if all documented "DROP (...) IF EXISTS" get binlogged. Left out DROP SERVER IF EXISTS because it seems that it only gets binlogged when using row event (see BUG#25705).
-
Bjorn Munch authored
Perl crashes when MTR 2 tries to start v1 Replaced require with system()
-
- 09 Feb, 2009 6 commits
-
-
Mats Kindahl authored
-
Davi Arnaut authored
-
Vladislav Vaintroub authored
Fix: use FormatMessage() to output system errors , not strerror()
-
Davi Arnaut authored
The problem is that a unfiltered user query was being passed as the format string parameter of sql_print_warning which later performs printf-like formatting, leading to crashes if the user query contains formatting instructions (ie: %s). Also, it was using THD::query as the source of the user query, but this variable is not meaningful in some situations -- in a delayed insert, it points to the table name. The solution is to pass the user query as a parameter for the format string and use the function parameter query_arg as the source of the user query.
-
Sergey Glukhov authored
added ignore-builtin-innodb option which disabled initialization of builtin InnoDB plugin
-
Vladislav Vaintroub authored
- /tmp directory is not guaranteed to exist on Windows. Use the value of environment variable TEMP here
-
- 07 Feb, 2009 5 commits
-
-
Timothy Smith authored
-
Timothy Smith authored
-
Timothy Smith authored
-
Joerg Bruehe authored
-
- 06 Feb, 2009 11 commits
-
-
Joerg Bruehe authored
-
Joerg Bruehe authored
This involves just the tag, no file changes - they were all present before.
-
Timothy Smith authored
-
Tatiana A. Nurnberg authored
-
Tatiana A. Nurnberg authored
In 37553 we declared longlong results for class Item_str_timefunc as per comments/docs, but didn't add a method for that. And the default just wasn't good enough for some cases. Changeset adds dedicated val_int() to class.
-
Mats Kindahl authored
TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported. There were two separate problems with the code, both of which are fixed with this patch: 1. An error was printed by InnoDB for TRUNCATE TABLE in statement mode when the in isolation levels READ COMMITTED and READ UNCOMMITTED since InnoDB does permit statement-based replication for DML statements. However, the TRUNCATE TABLE is not transactional, but is a DDL, and should therefore be allowed to be replicated as a statement. 2. The statement was not logged in mixed mode because of the error above, but the error was not reported to the client. This patch fixes the problem by treating TRUNCATE TABLE a DDL, that is, it is always logged as a statement and not reporting an error from InnoDB for TRUNCATE TABLE.
-
Timothy Smith authored
-
Magnus Svensson authored
- remove the disbling of all ssl_* tests now when certs are fixed.
-
Timothy Smith authored
-
Georgi Kodinov authored
-
Magnus Svensson authored
-