| 1 |
2008-02-29 Matthias Leich |
| 2 |
========================= |
| 3 |
|
| 4 |
1. The testsuite "funcs_1" is mostly intended for additional (compared |
| 5 |
to the common regression tests stored in mysql-test/t) checks |
| 6 |
of features (VIEWS, INFORMATION_SCHEMA, STORED PROCEDURES,...) |
| 7 |
introduced with MySQL 5.0. |
| 8 |
|
| 9 |
2. There were some extensions of this suite when new information_schema |
| 10 |
views were introduced. But in most cases the tests for these views |
| 11 |
were stored within the regression testsuite (mysql-test/t). |
| 12 |
|
| 13 |
INFORMATION_SCHEMA views introduced with MySQL 5.1 |
| 14 |
================================================== |
| 15 |
ENGINES (partially tested here) |
| 16 |
EVENTS (partially tested here) |
| 17 |
FILES |
| 18 |
GLOBAL_STATUS |
| 19 |
GLOBAL_VARIABLES |
| 20 |
PARTITIONS |
| 21 |
PLUGINS |
| 22 |
PROCESSLIST (full tested here) |
| 23 |
PROFILING |
| 24 |
REFERENTIAL_CONSTRAINTS |
| 25 |
SESSION_STATUS |
| 26 |
SESSION_VARIABLES |
| 27 |
|
| 28 |
3. Some hints for maintainers of this suite: |
| 29 |
- SHOW TABLES ... LIKE '<pattern>' |
| 30 |
does a case sensitive comparison between the tablename and |
| 31 |
the pattern. |
| 32 |
The names of the tables within the informationschema are in uppercase. |
| 33 |
So please use something like |
| 34 |
SHOW TABLES FOR information_schema LIKE 'TABLES' |
| 35 |
when you intend to get the same non empty result set on OS with and |
| 36 |
without case sensitive filesystems and default configuration. |
| 37 |
- The name of the data dictionary is 'information_schema' (lowercase). |
| 38 |
- Server on OS with filesystem with case sensitive filenames |
| 39 |
(= The files 'abc' and 'Abc' can coexist.) |
| 40 |
+ default configuration |
| 41 |
Example of behaviour: |
| 42 |
DROP DATABASE information_schema; |
| 43 |
ERROR 42000: Access denied for user ... to database 'information_schema' |
| 44 |
DROP DATABASE INFORMATION_SCHEMA; |
| 45 |
ERROR 42000: Access denied for user ... to database 'INFORMATION_SCHEMA' |
| 46 |
- Try to unify results by |
| 47 |
--replace_result $engine_type <engine_to_be_tested> |
| 48 |
if we could expect that the results for storage engine variants of a |
| 49 |
test differ only in the engine names. |
| 50 |
This makes future maintenance easier. |
| 51 |
- Avoid the use of include/show_msg*.inc. |
| 52 |
They produce "SQL" noise which annoys during server debugging and can be |
| 53 |
easy replaced by "--echo ...". |
| 54 |
|