mariadb/mysql-test
Andrei Elkin 7db8e76471 Bug #50192 Strange effect in replication test, trigger, auto_increment
The auto-inc unsafe warning makes sense even though it's just
one auto-inc table could be involved via a trigger or a stored
function.
However its content was not updated by bug@45677 fixes continuing to mention
two tables whereas the fixes refined semantics of replication of auto_increment 
in stored routine.

Fixed with updating the error message, renaming the error and an internal unsafe-condition 
constants.

A documentation notice
======================

      Inserting into an autoincrement column in a stored function or a trigger
      is unsafe for replication.
      Even with just one autoincrement column, if the routine is invoked more than 
      once slave is not guaranteed to execute the statement graph same way as 
      the master.
      And since it's impossible to estimate how many times a routine can be invoked at 
      the query pre-execution phase (see lock_tables), the statement is marked
      pessimistically unsafe.
2010-01-29 15:55:35 +02:00
..
collections Auto-merge from mysql-next-mr. 2010-01-25 19:16:45 +03:00
extra BUG#46364 MyISAM transbuffer problems (NTM problem) 2010-01-21 13:10:34 +00:00
include Auto-merge from mysql-next-mr. 2010-01-22 11:20:13 +03:00
lib Follup fix for WL#4738 2010-01-06 16:21:43 +01:00
r Auto-merge from mysql-next-mr. 2010-01-22 11:20:13 +03:00
std_data Backport of WL #2934: Make/find library for doing float/double 2009-12-22 19:23:13 +03:00
suite Bug #50192 Strange effect in replication test, trigger, auto_increment 2010-01-29 15:55:35 +02:00
t Auto-merge from mysql-next-mr. 2010-01-21 12:14:34 +03:00
Makefile.am WL#2360 Performance schema 2010-01-11 18:47:27 -07:00
mysql-stress-test.pl Checking in new version of 'mysql-stress-test.pl that was used for the last few month 2009-09-25 08:27:55 -07:00
mysql-test-run.pl WL#2360 Performance schema 2010-01-11 18:47:27 -07:00
purify.supp
README
README.gcov
README.stress
valgrind.supp fixed a typo in valgrind.supp 2009-09-25 14:52:41 +03: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