mariadb/mysql-test/suite/funcs_1
Sergey Vojtovich a7814d44fc MDEV-10311 - funcs_1.processlist_priv_no_prot fails sporadically
State column of SHOW PROCESSLIST can have NULL values for being initialized
threads (between new connection was acknowledged and waiting for network data).

Fixed test case to handle such cases by waiting for State to become empty
string.
2016-06-30 12:59:52 +04:00
..
bitdata copy from test-extra-5.0 to main tree 2007-02-06 19:07:48 +01:00
cursors Post fix for 2008-03-11 19:54:35 +01:00
datadict MDEV-10311 - funcs_1.processlist_priv_no_prot fails sporadically 2016-06-30 12:59:52 +04:00
include Rename std_data_ln to std_data. 2009-01-31 17:22:59 -02:00
lib copy from test-extra-5.0 to main tree 2007-02-06 19:07:48 +01:00
r Merge 5.3->5.5 2014-06-04 21:53:15 +04:00
storedproc merge with 5.3 2011-10-19 21:45:18 +02:00
t remove PBXT 2013-08-30 11:25:49 +02:00
triggers Fixed many funcs_1 tests after 43588 2010-03-19 09:56:26 +01:00
views MDEV-6528 review debian patches for mysql 2014-10-02 11:58:24 +02:00
disabled.def overlay support for mysql-test-run and mysqltest 2012-02-23 07:50:11 +01:00
README.txt Fix for 2008-03-31 19:48:02 +02:00

2008-02-29 Matthias Leich
=========================

1. The testsuite "funcs_1" is mostly intended for additional (compared
   to the common regression tests stored in mysql-test/t) checks
   of features (VIEWS, INFORMATION_SCHEMA, STORED PROCEDURES,...)
   introduced with MySQL 5.0.

2. There were some extensions of this suite when new information_schema
   views were introduced. But in most cases the tests for these views
   were stored within the regression testsuite (mysql-test/t).

   INFORMATION_SCHEMA views introduced with MySQL 5.1
   ==================================================
   ENGINES       (partially tested here)
   EVENTS        (partially tested here)
   FILES
   GLOBAL_STATUS
   GLOBAL_VARIABLES
   PARTITIONS
   PLUGINS
   PROCESSLIST   (full tested here)
   PROFILING
   REFERENTIAL_CONSTRAINTS
   SESSION_STATUS
   SESSION_VARIABLES

3. Some hints for maintainers of this suite:
   - SHOW TABLES ... LIKE '<pattern>'
     does a case sensitive comparison between the tablename and
     the pattern.
     The names of the tables within the informationschema are in uppercase.
     So please use something like
        SHOW TABLES FOR information_schema LIKE 'TABLES'
     when you intend to get the same non empty result set on OS with and
     without case sensitive filesystems and default configuration.
   - The name of the data dictionary is 'information_schema' (lowercase).
   - Server on OS with filesystem with case sensitive filenames
     (= The files 'abc' and 'Abc' can coexist.)
     + default configuration
     Example of behaviour:
     DROP DATABASE information_schema;
     ERROR 42000: Access denied for user ... to database 'information_schema'
     DROP DATABASE INFORMATION_SCHEMA;
     ERROR 42000: Access denied for user ... to database 'INFORMATION_SCHEMA'
   - Try to unify results by
     --replace_result $engine_type <engine_to_be_tested>
     if we could expect that the results for storage engine variants of a
     test differ only in the engine names.
     This makes future maintenance easier.
   - Avoid the use of include/show_msg*.inc.
     They produce "SQL" noise which annoys during server debugging and can be
     easy replaced by "--echo ...".