mirror of
https://github.com/MariaDB/server.git
synced 2025-09-02 09:41:40 +03:00
c7105d8008
Fix for shutdown on NT Fixed bug when using wrong dates from blob field. BitKeeper/deleted/.del-df_crash.result~4a3dbee64843953d: Delete: mysql-test/r/df_crash.result BitKeeper/deleted/.del-df_crash.test~4c365178fe437f6: Delete: mysql-test/t/df_crash.test Docs/manual.texi: Changelog innobase/ib_config.h.in: automatic changed file innobase/ib_config.h: automatic changed file mysql-test/r/func_time.result: Test case for bug in time functions mysql-test/r/innobase.result: Test for INSERT DELAYED mysql-test/t/func_time.test: Test case for bug in time functions mysql-test/t/innobase.test: Test for INSERT DELAYED scripts/mysql_convert_table_format.sh: Added --socket and --port sql/ha_innobase.cc: Fix bug when compiling with SAFE_MUTEX Cleaner comment when using SHOW TABLE STATUS sql/mysqld.cc: Fix for shutdown on NT sql/sql_insert.cc: Fixed problem with Innobase and INSERT DELAYED sql/sql_udf.cc: Support for UDF on windows sql/time.cc: Fixed bug when using wrong dates from blob field. strings/ctype-tis620.c: Removed not used variable support-files/mysql-max.spec.sh: Removed old not used section BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
This directory contains a test suite for mysql daemon. To run the currently existing test cases, simply execute ./mysql-test-run in this directory. It will fire up the newly built mysqld and test it. Note that you do not have to have to do make install, and you could actually have a co-existing MySQL installation - the tests will not conflict with it. All tests must pass. If one or more of them fail on your system, please read the following manual section of how to report the problem: http://www.mysql.com/doc/M/y/MySQL_test_suite.html You can create your own test cases. To create a test case: cd t vi test_case_name.test in the file, put a set of SQL commands that will create some tables, load test data, run some queries to manipulate it. We would appreciate if the test tables were called t1, t2, t3 ... (to not conflict too much with existing tables). Your test should begin by dropping the tables you are going to create and end by dropping them again. This will ensure that one can run the test over and over again. If you are using mysqltest commands (like result file names) in your test case you should do create the result file as follows: mysql-test-run --record test_case_name or mysqltest --record < t/test_case_name.test If you only have a simple test cases consistent of SQL commands and comments you can create the test case one of the following ways: mysql-test-run --record test_case_name mysql test < t/test_case_name.test > r/test_case_name.result mysqltest --record --record-file=r/test_case_name.result < t/test_case_name.test When this is done, take a look at r/test_case_name.result - If the result is wrong, you have found a bug; In this case you should edit the test result to the correct results so that we can verify that the bug is corrected in future releases. To submit your test case, put your .test file and .result file(s) into a tar.gz archive, add a README that explains the problem, ftp the archive to ftp://support.mysql.com/pub/mysql/secret/ and send a mail to bugs@lists.mysql.com