mariadb/mysql-test
igor@olga.mysql.com ce0be732d0 Fixed bug #24856: the result set of a ROLLUP query with DISTINCT could lack
some rollup rows (rows with NULLs for grouping attributes) if GROUP BY
list contained constant expressions.

This happened because the results of constant expressions were not put
in the temporary table used for duplicate elimination. In fact a constant
item from the GROUP BY list of a ROLLUP query can be replaced for an
Item_null_result object when a rollup row is produced . 

Now the JOIN::rollup_init function wraps any constant item referenced in
the GROYP BY list of a ROLLUP query into an Item_func object of a special
class that is never detected as constant item. This ensures creation of
fields for such  constant items in temporary tables and guarantees right
results when the result of the rollup operation first has to be written
into a temporary table, e.g. in the cases when duplicate elimination is
required.
2007-04-29 16:04:43 -07:00
..
include add --report-features to mysql-test-run.pl 2006-11-10 13:12:08 +01:00
lib MySQL versions before 5.0 still use cygwin, no need 2007-03-01 11:41:29 +01:00
misc
ndb reintroduce --no-defaults to ndb_mgmd 2006-01-20 00:08:26 +11:00
r Fixed bug #24856: the result set of a ROLLUP query with DISTINCT could lack 2007-04-29 16:04:43 -07:00
std_data Bug#23240 --init-file statements with NOW() reports '1970-01-01 11:00:00'as the date time 2007-02-19 09:37:34 +01:00
suite/jp
t Fixed bug #24856: the result set of a ROLLUP query with DISTINCT could lack 2007-04-29 16:04:43 -07:00
create-test-result
fix-result
install_test_db.sh mysql-test/install_test_db.sh 2006-11-09 17:43:31 +01:00
Makefile.am Bug#20166 mysql-test-run.pl does not test system privilege tables creation 2007-02-28 15:03:47 +01:00
my_create_tables.c
my_manage.c Some fixes to avoid compiler warnings. 2005-10-18 18:03:26 +03:00
my_manage.h
mysql-test-run-shell.sh Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1 2006-11-24 12:12:25 +01:00
mysql-test-run.pl Bug#27344 Total failure to start the server 2007-04-04 19:19:26 +02:00
mysql_test_run_new.c Some fixes to avoid compiler warnings. 2005-10-18 18:03:26 +03:00
README README: 2006-03-01 18:37:41 -06:00
README.gcov README.gcov: 2006-03-01 17:55:10 -06:00
resolve-stack
suppress.purify
valgrind.supp Valgrind error fixes 2007-02-01 18:00:24 +04:00

This directory contains a test suite for the 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 for instructions on how to report the
problem:

http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html

If you want to use an already running MySQL server for specific tests,
use the --extern option to mysql-test-run. Please note that in this mode,
the test suite expects you to provide the names of the tests to run.
For example, here is the command to run the "alias" and "analyze" tests
with an external server:

mysql-test-run --extern alias analyze

To match your setup, you might also need to provide --socket, --user, and
other relevant options.

With no test cases named on the command line, mysql-test-run falls back
to the normal "non-extern" behavior. The reason for this is that some
tests cannot run with an external server.


You can create your own test cases. To create a test case, create a new
file in the t subdirectory using a text editor. The file should have a .test
extension. For example:

 xemacs t/test_case_name.test

 In the file, put a set of SQL statements that create some tables,
 load test data, and run some queries to manipulate it.

 We would appreciate it if you name your test tables 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 ensures that you can run the test over
 and over again.
 
 If you are using mysqltest commands (like result file names) in your
 test case, you should 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 consisting of SQL statements and
 comments, you can create the test case in 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 incorrect, 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