mariadb

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

History

unknown 2fc5d274e8 Fixing bug #8850 in such a way that when TRUNCATE is called within stored procedure, it is converted to DELETE. mysql-test/r/sp.result: A result for the test case for bug #8850 mysql-test/t/sp.test: A test case for the bug #8850 sql/sql_delete.cc: A fix for bug #8850, plus adding a missing call to mysql_init_select(), which caused mem_root corruption. sql/sql_parse.cc: A fix for the bug #8850 BitKeeper/etc/ignore: Added acinclude.m4 to the ignore list		2005-03-05 21:44:15 +02:00
..
include	Merge	2005-02-07 18:05:11 +01:00
lib	init_db.sql:	2005-02-17 05:22:14 +01:00
misc
ndb	ndb_port_base is obsolete with WL#2278	2005-02-09 19:29:37 +01:00
r	Fixing bug #8850 in such a way that when TRUNCATE is called within	2005-03-05 21:44:15 +02:00
std_data	fix rpl_trunc_binlog to test the new behaviour	2005-02-19 22:24:13 +01:00
suite/jp
t	Fixing bug #8850 in such a way that when TRUNCATE is called within	2005-03-05 21:44:15 +02:00
create-test-result
fix-result
init_db.sql
install_test_db.sh
Makefile.am	make_binary_distribution.sh, Makefile.am:	2005-02-17 20:07:52 +01:00
my_create_tables.c	merge	2005-02-09 19:13:20 +05:00
my_manage.c	merge	2005-02-09 19:13:20 +05:00
my_manage.h
mysql-test-run.pl	Merge poseidon.ndb.mysql.com:/home/tomas/mysql-5.0	2005-02-17 09:37:07 +01:00
mysql-test-run.sh	Merge	2005-02-23 10:29:31 +01:00
mysql_test_run_new.c	merge	2005-02-09 19:13:20 +05:00
README
README.gcov
resolve-stack

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.

If you want to run the test with a running MySQL server use the --external
option to mysql-test-run.

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://dev.mysql.com/doc/mysql/en/MySQL_test_suite.html


You can create your own test cases. To create a test case:

 xeamacs t/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