mariadb/mysql-test
msvensson@neptunus.(none) dcf0f346cf Bug#20589 Missing some table level privileges after upgrade
- The table_priv column of table_privs table was altered to a enum type
   with fewer enums causing the SHOW/CREATE VIEW grants to be truncated.
 - Improved comments and moved all declarations for table_privs, column_privs
   and proc_privs to one section for each table making it easy to see hat alterations
   are performed on each table
 - Reduced the number of ALTER's slightly, but as this is an upgrade script we need
   to take all possibilites into account.
2006-11-29 12:04:29 +01:00
..
include Merge kahlann.erinye.com:/home/df/mysql/build/mtr-4.1 2006-11-10 13:14:21 +01:00
lib Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint 2006-11-21 15:58:05 +01:00
misc
ndb
r Bug#20589 Missing some table level privileges after upgrade 2006-11-29 12:04:29 +01:00
std_data Bug#21868 Server crashes if encrypted certificate key provided 2006-09-25 16:44:15 +02:00
suite/jp
t Bug#20589 Missing some table level privileges after upgrade 2006-11-29 12:04:29 +01:00
create-test-result
fix-result
init_db.sql
install_test_db.sh
Makefile.am Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint 2006-11-14 09:43:30 +01:00
my_create_tables.c
my_manage.c
my_manage.h
mysql-stress-test.pl
mysql-test-run-shell.sh Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint 2006-11-13 19:19:02 +01:00
mysql-test-run.pl When runnig from binary dist the .sql files are found in share/ directory 2006-11-21 21:39:37 +01:00
mysql_test_run_new.c
README
README.gcov
README.stress
resolve-stack
suppress.purify
valgrind.supp Add suppressions seen on maint1, nothing new just a nother version of libc 2006-09-27 18:10:15 +02: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