mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-01-18 13:02:28 +01:00

History

guilhem@mysql.com 3b974039f7 -- Waiting for Monty's approval before push -- Bug 571: play LOAD DATA INFILE the same way on the slave as it was on the master: if it was with IGNORE, do it with IGNORE, if it was with REPLACE, do it with REPLACE, and (the change) if it was with nothing, do it with nothing (not with IGNORE !!). Bug 573: print a proper error message in case of duplicate entry in LOAD DATA INFILE on the slave, i.e. a message where the keyname and key value appear : 'Duplicate entry '1' for key 1' and not 'Duplicate entry '%-.64s' for key %d'		2003-06-03 15:47:29 +02:00
..
include	Openssl test	2003-03-11 13:41:53 +04:00
misc	Fixed that LOAD DATA INFILE works with transactions.	2001-08-28 06:43:55 +03:00
r	-- Waiting for Monty's approval before push --	2003-06-03 15:47:29 +02:00
std_data	Merge eagle.mysql.r18.ru:/home/vva/work/mysql.orig/clear/mysql-4.0	2003-05-21 14:58:11 -04:00
t	-- Waiting for Monty's approval before push --	2003-06-03 15:47:29 +02:00
create-test-result	Removed not used functions from sql_cache	2001-12-14 16:02:41 +02:00
fix-result	fixed problem in rpl_log test	2001-11-19 12:03:30 -07:00
install_test_db.sh	Added CREATE TEMPORARY TABLES and LOCK TABLES to db and host tables	2002-09-16 15:55:19 +03:00
Makefile.am	- added missing file mysql-test/std_data/des_key_file to source and binary	2003-03-04 18:18:05 +01:00
mysql-test-run.sh	Fixed problem with mysql prompt when server disconnect. (Bug 356)	2003-05-27 16:40:14 +03:00
README	Fixed bug in MAX() optimizing for BDB tables	2001-03-10 17:05:10 +02:00
README.gcov	fixes for parallel make, re-added the lost README files in mysql-test	2000-12-13 18:23:55 -07:00
resolve-stack	Here comes a nasty patch, although I am not ready to push it yet. I will	2002-01-19 19:16:52 -07:00

README

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