mariadb/mysql-test
unknown 5a42525027 fixed union types merging and table related metadata (BUG#8824)
mysql-test/r/func_group.result:
  new result
mysql-test/r/metadata.result:
  new result
  test of metadata of variables, unions and derived tables
mysql-test/r/union.result:
  new results
  test of union of enum
mysql-test/t/metadata.test:
  test of metadata of variables, unions and derived tables
mysql-test/t/union.test:
  test of union of enum
sql/field.cc:
  Field type merging rules added
  Fixed table name/alias returting for field made from temporary tables
sql/field.h:
  removed unned field type reporting
sql/item.cc:
  fixed bug in NEW_DATE type field creartion
  replaced mechanism of merging types of UNION
sql/item.h:
  replaced mechanism of merging types of UNION
sql/item_func.h:
  new item type to make correct field type detection possible
sql/item_subselect.cc:
  added table name parameter to prepare() to show right table alias for derived tables
sql/sql_derived.cc:
  added table name parameter to prepare() to show right table alias for derived tables
sql/sql_lex.h:
  added table name parameter to prepare() to show right table alias for derived tables
sql/sql_parse.cc:
  made function for enum/set pack length calculation
sql/sql_prepare.cc:
  added table name parameter to prepare() to show right table alias for derived tables
sql/sql_select.cc:
  new temporary table field creation by Item_type_holder
  fixed table alias for temporary table
sql/sql_union.cc:
  added table name parameter to prepare() to show right table alias for derived tables
2005-03-23 08:36:48 +02:00
..
include Fix for Bug #8753 Invalid schema object version after dropping index 2005-03-07 10:21:38 +01:00
lib Keep the Perl version of 'mysql-test-run' in sync with the shell script. 2005-03-11 11:08:27 +01:00
misc
ndb backported ndb_mgm options from 5.0 2005-01-25 10:03:27 +01:00
r fixed union types merging and table related metadata (BUG#8824) 2005-03-23 08:36:48 +02:00
std_data merge with 4.0 2004-11-12 11:17:53 +02:00
suite/jp Many files: 2005-01-07 14:32:05 +02:00
t fixed union types merging and table related metadata (BUG#8824) 2005-03-23 08:36:48 +02:00
create-test-result
fix-result
init_db.sql replaced init_db.sql 2004-11-10 15:03:59 +05:00
install_test_db.sh added 2 masters for ndb tests 2004-09-28 17:04:30 +00:00
Makefile.am mysql-test-run to default run with ndbcluster if compiled with that support 2005-03-07 13:42:01 +01:00
my_create_tables.c WL#964 2005-01-31 19:18:06 +05:00
my_manage.c WL#964 2005-02-02 19:53:49 +05:00
my_manage.h corrected mysqltest.dsp 2004-12-14 18:46:55 +05:00
mysql-test-run.pl mysql-test-run.pl: 2005-03-09 01:34:22 +01:00
mysql-test-run.sh Merge mysql.com:/M41/mysql-4.1 into mysql.com:/M41/push-4.1 2005-03-10 20:31:05 +01:00
mysql_test_run_new.c WL#964 2005-02-02 19:53:49 +05:00
README
README.gcov
resolve-stack

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