mirror of
https://github.com/MariaDB/server.git
synced 2025-01-20 22:12:30 +01:00
89ddc0aa52
Bug#35335 funcs_1: Some tests fail within load_file during
pushbuild runs
Solution: 1. Move files with input data used in load_file,
load data etc.
from suite/funcs_1/<whatever>
to std_data
2. Use for testsuite funcs_1 the server option
--secure-file-priv=<MYSQLTEST_VARDIR>
3. Outfiles have to be stored under MYSQLTEST_VARDIR
+ changes according to WL#4304 Cleanup in funcs_1 tests
- backport of fixes/improvements made in 5.1 to 5.0
The differences between scripts in 5.0 and 5.1 cause
much additional and annoying work during any upmerge.
- replace error numbers with names
- improved comments
- improved formatting
- Unify storage engine names so that result files for
storage engine variants do not differ (some tests)
- remove a script no more used (tests are done in other scripts)
54 lines
2.2 KiB
Text
54 lines
2.2 KiB
Text
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 ...".
|
|
|