mirror of
https://github.com/MariaDB/server.git
synced 2025-01-22 23:04:20 +01:00
30091e23f9
testsuite funcs_1
1. Fix the following bugs
Bug#30440 "datadict" tests (all engines) fail: Character sets depend on configuration
Solution: Test variants charset_collation_* adjusted to different builds
Bug#32603 "datadict" tests (all engines) fail in "community" tree: "PROFILING" table
Solution: Excluding "PROFILING" table from queries
Bug#33654 "slow log" is missing a line
Solution: Unify the content of the fields TABLES.TABLE_ROWS and
STATISTICS.CARDINALITY within result sets
Bug#34532 Some funcs_1 tests do not clean up at end of testing
Solution: DROP objects/reset global server variables modified during testing
+ let tests missing implementation end before loading of tables
Bug#31421 funcs_1: ndb__datadict fails, discrepancy between scripts and expected results
Solution: Cut <engine>__datadict tests into smaller tests + generate new results.
Bug#33599 INFORMATION_SCHEMA.STATISTICS got a new column INDEX_COMMENT: tests fail (2)
Generation of new results during post merge fix
Bug#33600 CHARACTER_OCTET_LENGTH is now CHARACTER_MAXIMUM_LENGTH * 4
Generation of new results during post merge fix
Bug#33631 Platform-specific replace of CHARACTER_MAXIMUM_LENGTH broken by 4-byte encoding
Generation of new results during post merge fix
+ removal of platform-specific replace routine (no more needed)
2. Restructure the tests
- Test not more than one INFORMATION_SCHEMA view per testscript
- Separate tests of I_S view layout+functionality from content related to the
all time existing databases "information_schema", "mysql" and "test"
- Avoid storage engine related variants of tests which are not sensible to
storage engines at all.
3. Reimplement or add some subtests + cleanup
There is a some probability that even the reviewed changeset
- does not fix all bugs from above or
- contains new bugs which show up on some platforms <> Linux or on one of
the various build types
4. The changeset contains fixes according to
- one code review
- minor bugs within testing code found after code review (accepted by reviewer)
- problems found during tests with 5.0.56 in build environment
46 lines
1.7 KiB
Text
46 lines
1.7 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:
|
|
- 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'
|
|
|