- 04 Jun, 2008 1 commit
-
-
Mattias Jonsson authored
-
- 03 Jun, 2008 3 commits
-
-
Davi Arnaut authored
if cached query uses many tables The problem was that query cache would not properly cache queries which used 256 or more tables but yet would leave behind query cache blocks pointing to freed (destroyed) data. Later when invalidating (due to a truncate) query cache would attempt to grab a lock which resided in the freed data, leading to hangs or undefined behavior. This was happening due to a improper return value from the function responsible for registering the tables used in the query (so the cache can be invalidated later if one of the tables is modified). The function expected a return value of type boolean (char, 8 bits) indicating success (1) or failure (0) but the number of tables registered (unsigned int, 32 bits) was being returned instead. This caused the function to return failure for cases where it had actually succeed because when a type (unsigned int) is converted to a narrower type (char), the excess bits on the left are discarded. Thus if the 8 rightmost bits are zero, the return value will be 0 (failure). The solution is to simply return true (1) only if the number of registered table is greater than zero and false (0) otherwise. mysql-test/r/query_cache_merge.result: Add test case result for Bug#33362 mysql-test/t/query_cache_merge.test: Add test case for Bug#33362 sql/sql_cache.cc: Return 1 or 0 depending on the number of registered tables.
-
Mattias Jonsson authored
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. mysql-test/r/innodb-replace.result: Bug#31210: INSERT DELAYED crashes server when used on partitioned tables changed error message mysql-test/t/innodb-replace.test: Bug#31210: INSERT DELAYED crashes server when used on partitioned tables changed error message mysql-test/t/merge.test: Bug#31210: INSERT DELAYED crashes server when used on partitioned tables changed error message mysql-test/t/partition_hash.test: Bug#31210: INSERT DELAYED crashes server when used on partitioned tables changed error message sql/share/errmsg.txt: Bug#31210: INSERT DELAYED crashes server when used on partitioned tables added error message for tables not supporting DELAYED sql/sql_insert.cc: Bug#31210: INSERT DELAYED crashes server when used on partitioned tables changed error message
-
Matthias Leich mleich@mysql.com authored
Bug 36788 Multiple funcs_1 'trig' tests are failing on vanilla builds
-
- 02 Jun, 2008 1 commit
-
-
Matthias Leich mleich@mysql.com authored
Fix for this bug and additional improvements/fixes In detail: - Remove unicode attribute from several columns (unicode properties were nowhere needed/tested) of the table tb3 -> The runnability of these tests depends no more on the availibility of some optional collations. - Use a table tb3 with the same layout for all engines to be tested and unify the engine name within the protocols. -> <engine>_trig_<abc>.result have the same content - Do not load data into tb3 if these rows have no impact on result sets - Add tests for NDB (they exist already in 5.1) - "--replace_result" at various places because NDB variants of tests failed with "random" row order in results This fixes a till now unknown weakness within the funcs_1 NDB tests existing in 5.1 and 6.0 - Fix the expected result of ndb_trig_1011ext which suffered from Bug 32656 + disable this test - funcs_1 could be executed with the mysql-test-run.pl option "--reorder", which saves some runtime by optimizing server restarts. Runtimes on tmpfs (one attempt only): with reorder 132 seconds without reorder 183 seconds - Adjust two "check" statements within func_misc.test which were incorrect (We had one run with result set difference though the server worked good.) - minor fixes in comments
-
- 30 May, 2008 2 commits
-
-
Patrick Crews authored
-
Patrick Crews authored
-
- 29 May, 2008 2 commits
-
-
Matthias Leich mleich@mysql.com authored
Upmerge of fix for this bug and a second similar problem found during experimenting. This replaces the first fix (already pushed to 5.1 and merged to 6.0) which - failed in runs with the embedded server - cannot be ported back to 5.0
-
Matthias Leich mleich@mysql.com authored
Fix for this bug and a second similar problem found during experimenting. This replaces the first fix (already pushed to 5.1 and merged to 6.0) which - failed in runs with the embedded server - cannot be ported back to 5.0
-
- 28 May, 2008 4 commits
-
-
Georgi Kodinov authored
-
Georgi Kodinov authored
-
Georgi Kodinov authored
sql/share/charsets/README: merged bug 36676 to 5.1-bugteam strings/CHARSET_INFO.txt: merged bug 36676 to 5.1-bugteam
-
Alexander Barkov authored
Thanks to Paul for preparing the up-to-date files reflecting 4.1 changes.
-
- 27 May, 2008 4 commits
-
-
Patrick Crews authored
Bug#36724 - Test funcs_1.<engine>_storedproc_02 needs to be updated Bug#36726 - Test funcs_1.<engine>_storedproc failing - Needs to be updated on 5.1+ func_view bug: re-records .result files to account for addition of charset and collation data to SHOW CREATE VIEW output storedproc bugs: Added expected errors for those storedprocs that use SQLSTATE:00000 in their handlers. re-recorded .result files to account for these expected errors. mysql-test/suite/funcs_1/r/innodb_func_view.result: Update result set for changes to SHOW CREATE VIEW output mysql-test/suite/funcs_1/r/memory_func_view.result: Updated result set due to changes in SHOW CREATE VIEW output mysql-test/suite/funcs_1/r/myisam_func_view.result: Updated result set due to changes in SHOW CREATE VIEW output
-
Davi Arnaut authored
-
Davi Arnaut authored
BUILD/compile-pentium-valgrind-max-no-ndb: Disable ndb.
-
Georgi Kodinov authored
There was a typo in a error check causing wrong thing to be ckecked and a possible error not being caught. Fixed by using the correct variable to test for malloc() errors. tests/mysql_client_test.c: Bug #36887: fixed a typo
-
- 26 May, 2008 1 commit
-
-
Sven Sandberg authored
rpl_slave_status failed on pushbuild. The slave stopped with an error. Adding sync_slave_with_master fixes the problem. Updated test case. mysql-test/suite/rpl/r/rpl_slave_status.result: Updated result file. mysql-test/suite/rpl/t/rpl_slave_status.test: - Added comment explaining what the test does. - Added sync_slave_with_master in two places where it was missing. This caused sporadic pushbuild errors. - Added wait_for_slave_to_{start,stop} after {START,STOP} SLAVE queries. - Removed 'drop table if exists' from setup code. - Replaced save_master_pos;connection slave;sync_with_master by sync_slave_with_master. - Replaced 'delete from mysql.user' by 'drop user'. - Wrapped 'show slave status' inside query_get_value(), so that only what we test is in the output.
-
- 23 May, 2008 5 commits
-
-
Chad MILLER authored
-
Chad MILLER authored
-
Chad MILLER authored
-
Chad MILLER authored
-
Bug#36345 Test 'func_misc' fails on RHAS3 x86_64 and a second similar problem within this test found during experimenting.
-
- 22 May, 2008 2 commits
-
-
Chad MILLER authored
-
Chad Miller authored
-
- 21 May, 2008 5 commits
-
-
Chad MILLER authored
-
Kristofer Pettersson authored
mysql-test/r/status.result: reverted merging misstake mysql-test/t/status.test: reverted merging misstake
-
Kristofer Pettersson authored
The Diagnostic_area caused an assertion failure in debug mode when the disk was full. By setting the internal error handler to ignore errors caused by underlying logging methods, the error is avoided. sql/log.cc: MYSQL_QUERY_LOG::write uses IOCACHE for writing data. If writing fails an error is pushed by the procedure my_error which in turn invokes the default error handler my_message_sql. When the error is set the Diagnostic_area status changes and later trigger an assertion on the next consecutive status change which happens by for example the function my_ok(). By intercepting the error handler from the logger interface this error can be silenced.
-
unknown authored
-
Kristofer Pettersson authored
The failing test case is depending on unnecessary status variable output which changes based on build configuration. By reducing the output the test becomes more stable. mysql-test/r/status.result: Modified test case mysql-test/t/disabled.def: Enabled status.test mysql-test/t/status.test: Modified test case.
-
- 20 May, 2008 8 commits
-
-
unknown authored
and table DDL changed after PREPARE" to pass in embedded mode. mysql-test/r/ps.result: Update results (Bug#27430) mysql-test/r/ps_ddl.result: Update results (Bug#27430) mysql-test/t/ps.test: Add a test case for Bug#27430. ps.test is not run in --embedded-server, thus it now contains the part of the test for Bug#27430 that doesn't work in embedded server. mysql-test/t/ps_ddl.test: Move a part of the test for Bug#27430 that doesn't work in embedded server to ps.test, that includes not_embedded.inc.
-
unknown authored
the local tree contains a fix for Bug#32748 "Inconsistent handling of assignments to general_log_file/slow_query_log_file", which changes output of a number of tests. mysql-test/r/general_log_file_basic.result: Update results (Bug#32748) mysql-test/r/log_output_basic.result: Update the test with results of the fix for Bug#32748 mysql-test/r/slow_query_log_file_basic.result: Update the test with results of the fix for Bug#32748 mysql-test/t/general_log_file_basic.test: Adjust to take into account the fix for Bug#32748 (a port from 6.0-bugteam) mysql-test/t/log_output_basic.test: Adjust to take into account the fix for Bug#32748 (a port from 6.0-bugteam) mysql-test/t/slow_query_log_file_basic.test: Adjust to take into account the fix for Bug#32748 (a port from 6.0-bugteam) tests/mysql_client_test.c: Fix a compilation warning.
-
unknown authored
after PREPARE" Update test results after a merge with the main tree: the new minimum for the table definition cache is 256. mysql-test/r/table_definition_cache_basic.result: Update test results: the new minimum for table definition cache is 256
-
unknown authored
PREPARE", review fixes: - make the patch follow the specification of WL#4166 and remove the new error that was originally introduced. Now the client never gets an error from reprepare, unless it failed. I.e. even if the statement at hand returns a completely different result set, this is not considered a server error. The C API library, that can not handle this situation, was modified to return a client error. Added additional test coverage. include/errmsg.h: Add a new client side error: now when we automatically reprepare a statement, the new result set may contain a different number of columns. include/mysql_com.h: Add a new server status to be sent to the client if the number of columns in the result set is different. libmysql/errmsg.c: Add a new error message. libmysql/libmysql.c: Make the client library robust against a result set that contains a different number of columns from prepare time. Previously that could never happen, and we simply had an assert. That means in particular that all clients are advised to upgrade with transition to 5.1, if they are using prepared statements C API. Make mysql_stmt_store_result() and mysql_stmt_execute() robust against "broken" statement handles (those that have an error). sql/sql_parse.cc: Clear transient server status flags at start of statement more systematically. sql/share/errmsg.txt: Remove an error that is unused and is not part of any public release. sql/sql_prepare.cc: Instead of returning an error in case the number of result set columns has changed, simply update the client in server status. That will allow modern clients automatically recover from an error. tests/mysql_client_test.c: Add additional coverage to the cases when the number of result set columns changed as a result of reprepare. Cover conversion and truncation of result set columns.
-
Chad MILLER authored
The test is vulnerable because it does not check if slave has stopped at time of the new session is requested `start slave;' Fixed with deploying explicitly wait_for_slave_to_stop synchronization macro.
-
unknown authored
into bodhi.(none):/opt/local/work/mysql-5.1-27430 Makefile.am: Auto merged include/my_global.h: Auto merged mysql-test/include/mix1.inc: Auto merged sql/item.cc: Auto merged sql/my_decimal.h: Auto merged sql/mysqld.cc: Auto merged sql/set_var.cc: Auto merged sql/set_var.h: Auto merged sql/sp.cc: Auto merged sql/sp_head.cc: Auto merged sql/sql_base.cc: Auto merged sql/sql_class.cc: Auto merged sql/sql_class.h: Auto merged sql/sql_parse.cc: Auto merged sql/sql_table.cc: Auto merged sql/sql_update.cc: Auto merged sql/share/errmsg.txt: Auto merged sql/sql_yacc.yy: Auto merged libmysqld/CMakeLists.txt: Manual merge. libmysqld/lib_sql.cc: Manual merge. mysql-test/t/disabled.def: Manual merge.
-
unknown authored
into bodhi.(none):/opt/local/work/mysql-5.1-27430 sql/sql_base.cc: Manual merge.
-
unknown authored
PREPARE": rename members, methods, classes to follow the spec (a code review request) sql/mysql_priv.h: enum_metadata_type -> enum_table_ref_type sql/sp_head.cc: Metadata_version_observer -> Reprepare_observer sql/sql_base.cc: metadata -> table_ref sql/sql_class.cc: Replace an abstract interface with a concrete implementation. sql/sql_class.h: enum_metadata_type -> enum_table_ref_type sql/sql_prepare.cc: Move implementation of Execute_observer to sql_class.cc and rename the class to Reprepare_observer. Use getters instead of direct access to the members. sql/table.h: metadata -> table_ref
-
- 19 May, 2008 2 commits
-
-
unknown authored
Add test target to the makefile that will cause all statements to be re-prepared before execution. Makefile.am: Add test-reprepare target. In combination with the --ps-protocol this will cause that every statement in the test suite be re-prepared before execution. sql/sql_base.cc: Re-prepare each statement before execution.
-
unknown authored
into mysql.com:/d2/hf/mysql-5.1-bugteam
-