- 31 Jan, 2009 4 commits
-
-
Davi Arnaut authored
test case was executed.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
- 30 Jan, 2009 5 commits
-
-
Horst Hunger authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
- 29 Jan, 2009 14 commits
-
-
Joerg Bruehe authored
-
Luis Soares authored
conflicts: Text conflict in mysql-test/suite/sys_vars/r/rpl_max_binlog_size_func.result Text conflict in mysql-test/suite/sys_vars/t/rpl_max_binlog_size_func.test
-
Luis Soares authored
-
Magnus Svensson authored
-
Magnus Svensson authored
- Increase number of transaction objects available in ndbd - Most likely this is a timing related issue.
-
Andrei Elkin authored
Temporarily blocking to run the test on windows. Todo: remove the include upon setup_fake_relay_log has been fixed.
-
Alfranio Correia authored
BUG#41003 reached our trees.
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
If the system time is adjusted back during a query execution (resulting in the end time being earlier than the start time) the code that prints to the slow query log gets confused and prints unsigned negative numbers. Fixed by not logging the statements that would have negative execution time due to time shifts. No test case since this would involve changing the system time.
-
Satya B authored
-
Satya B authored
After the earlier fix, mtr tests reports "table full" messages as warnings. This is expected, this patch fixes the mtr testframework to ignore the error message.
-
Alfranio Correia authored
-
Sergey Petrunia authored
-
- 28 Jan, 2009 17 commits
-
-
Sergey Petrunia authored
-
Sergey Petrunia authored
Item_in_optimizer::is_null() evaluated "NULL IN (SELECT ...)" to NULL regardless of whether subquery produced any records, this was a documented limitation. The limitation has been removed (see bugs 8804, 24085, 24127) now Item_in_optimizer::val_int() correctly handles all cases with NULLs. Make Item_in_optimizer::is_null() invoke val_int() to return correct values for "NULL IN (SELECT ...)".
-
Gleb Shchepa authored
-
Gleb Shchepa authored
messed up "ROW(...) IN (SELECT ... FROM DUAL)" always returned TRUE. Item_in_subselect::row_value_transformer rewrites "ROW(...) IN SELECT" conditions into the "EXISTS (SELECT ... HAVING ...)" form. For a subquery from the DUAL pseudotable resulting HAVING condition is an expression on constant values, so further transformation with optimize_cond() eliminates this HAVING condition and resets JOIN::having to NULL. Then JOIN::exec treated that NULL as an always-true-HAVING and that caused a bug. To distinguish an optimized out "HAVING TRUE" clause from "HAVING FALSE" we already have the JOIN::having_value flag. However, JOIN::exec() ignored JOIN::having_value as described above as if it always set to COND_TRUE. The JOIN::exec method has been modified to take into account the value of the JOIN::having_value field.
-
Davi Arnaut authored
-
Magnus Svensson authored
-
Magnus Svensson authored
- Fix faulty regex used for filtering out suspicious warnings, causing warnings/errors from previous tests to be reported
-
Davi Arnaut authored
Dirty close tricky does not work on Windows.
-
Luis Soares authored
BUG#42383 2009-01-28 lsoares "This fails in embedded and on windows. Note that this test is not run on windows and on embedded in PB for main trees currently"
-
Georgi Kodinov authored
-
Alfranio Correia authored
When using CREATE TEMPORARY TABLE LIKE to create a temporary table, or using TRUNCATE to delete all rows of a temporary table, they did not set the tmp_table_used flag, and cause the omission of "SET @@session.pseudo_thread_id" when dumping binlog with mysqlbinlog, and cause error when replay the statements. This patch fixed the problem by setting tmp_table_used in these two cases. (Done by He Zhenxing 2009-01-12)
-
Georgi Kodinov authored
Re-generated the PKI files needed. Removed the ones that are not needed. Updated the tests to reference the correct SSL subject.
-
Bjorn Munch authored
-
Bjorn Munch authored
Check for existence of diff fails on Solaris due to unsupported "-v" Fix is to do this check only on Windows where it was needed
-
Satya B authored
When a MEMORY table is full the error is returned to client but not written to error log. Fixed the handler api to write the error mesage to error log when the table is full. Note: No TestCase included as testing the error log is non-trivial.
-
Alfranio Correia authored
-
Magnus Svensson authored
- Disable the two patterns that previously have been faulty - for now.
-