Merge mysql.com:/home/mydev/mysql-4.0

4.  Price and payment.

No later than thirty (30) days after submission of the Order Form, Licensee

shall remit one non-refundable license fee per Licensed Copy as posted on

http://order.mysql.com on the date Licensee submitted the Order Form (the

http://shop.mysql.com on the date Licensee submitted the Order Form (the

"License Fee"). All payments shall be made in Euros or U.S. dollars. Licensee

shall be responsible for paying all local, state, federal and international

sales, value added, excise and other taxes and duties payable in connection

For further information about MySQL or additional documentation, see:

- The latest information about MySQL: http://www.mysql.com

- The current MySQL documentation: http:/dev.mysql.com/doc

- The current MySQL documentation: http://dev.mysql.com/doc

Some manual sections of special interest:

[AC_CHECK_LIB(ncurses, tgetent, mysql_cv_termcap_lib=libncurses,

    [AC_CHECK_LIB(curses, tgetent, mysql_cv_termcap_lib=libcurses,

	[AC_CHECK_LIB(termcap, tgetent, mysql_cv_termcap_lib=libtermcap,

	    mysql_cv_termcap_lib=NOT_FOUND)])])])

	    [AC_CHECK_LIB(tinfo, tgetent, mysql_cv_termcap_lib=libtinfo,

	      mysql_cv_termcap_lib=NOT_FOUND)])])])])

AC_MSG_CHECKING(for termcap functions library)

if test "$mysql_cv_termcap_lib" = "NOT_FOUND"; then

AC_MSG_ERROR([No curses/termcap library found])

TERMCAP_LIB=-ltermcap

elif test "$mysql_cv_termcap_lib" = "libncurses"; then

TERMCAP_LIB=-lncurses

elif test "$mysql_cv_termcap_lib" = "libtinfo"; then

TERMCAP_LIB=-ltinfo

else

TERMCAP_LIB=-lcurses

fi

if test "$IS_LINUX" = "true"; then

  AC_MSG_CHECKING([for atomic operations])

  AC_LANG_SAVE

  AC_LANG_CPLUSPLUS

  atom_ops=

  AC_TRY_RUN([

#include <asm/atomic.h>

  if test -z "$atom_ops"; then atom_ops="no"; fi

  AC_MSG_RESULT($atom_ops)

  AC_LANG_RESTORE

  AC_ARG_WITH(pstack,

    [  --with-pstack           Use the pstack backtrace library],

    [ USE_PSTACK=$withval ],

This directory contains a test suite for mysql daemon. To run

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

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:

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.

http://dev.mysql.com/doc/mysql/en/MySQL_test_suite.html

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:

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:

 cd t

 vi test_case_name.test

 xemacs 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.

 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 if the test tables were called t1, t2, t3 ... (to not

 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 will ensure that one can run the test

 over and over again.

 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 do create the result file as follows:

 test case, you should create the result file as follows:

 mysql-test-run --record test_case_name

 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:

 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

 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

 - 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.