You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

635 lines
23 KiB

WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
WL#4203 Reorganize and fix the data dictionary tests of 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
18 years ago
  1. SHOW TABLES FROM information_schema LIKE 'ROUTINES';
  2. Tables_in_information_schema (ROUTINES)
  3. ROUTINES
  4. #######################################################################
  5. # Testcase 3.2.1.1: INFORMATION_SCHEMA tables can be queried via SELECT
  6. #######################################################################
  7. DROP VIEW IF EXISTS test.v1;
  8. DROP PROCEDURE IF EXISTS test.p1;
  9. DROP FUNCTION IF EXISTS test.f1;
  10. CREATE VIEW test.v1 AS SELECT * FROM information_schema.ROUTINES;
  11. CREATE PROCEDURE test.p1() SELECT * FROM information_schema.ROUTINES;
  12. CREATE FUNCTION test.f1() returns BIGINT
  13. BEGIN
  14. DECLARE counter BIGINT DEFAULT NULL;
  15. SELECT COUNT(*) INTO counter FROM information_schema.ROUTINES;
  16. RETURN counter;
  17. END//
  18. # Attention: The printing of the next result sets is disabled.
  19. SELECT * FROM information_schema.ROUTINES;
  20. SELECT * FROM test.v1;
  21. CALL test.p1;
  22. SELECT test.f1();
  23. DROP VIEW test.v1;
  24. DROP PROCEDURE test.p1;
  25. DROP FUNCTION test.f1;
  26. #########################################################################
  27. # Testcase 3.2.8.1: INFORMATION_SCHEMA.ROUTINES layout
  28. #########################################################################
  29. DESCRIBE information_schema.ROUTINES;
  30. Field Type Null Key Default Extra
  31. SPECIFIC_NAME varchar(64) NO
  32. ROUTINE_CATALOG varchar(512) YES NULL
  33. ROUTINE_SCHEMA varchar(64) NO
  34. ROUTINE_NAME varchar(64) NO
  35. ROUTINE_TYPE varchar(9) NO
  36. DTD_IDENTIFIER varchar(64) YES NULL
  37. ROUTINE_BODY varchar(8) NO
  38. ROUTINE_DEFINITION longtext YES NULL
  39. EXTERNAL_NAME varchar(64) YES NULL
  40. EXTERNAL_LANGUAGE varchar(64) YES NULL
  41. PARAMETER_STYLE varchar(8) NO
  42. IS_DETERMINISTIC varchar(3) NO
  43. SQL_DATA_ACCESS varchar(64) NO
  44. SQL_PATH varchar(64) YES NULL
  45. SECURITY_TYPE varchar(7) NO
  46. CREATED datetime NO 0000-00-00 00:00:00
  47. LAST_ALTERED datetime NO 0000-00-00 00:00:00
  48. SQL_MODE varchar(8192) NO
  49. ROUTINE_COMMENT varchar(64) NO
  50. DEFINER varchar(77) NO
  51. CHARACTER_SET_CLIENT varchar(32) NO
  52. COLLATION_CONNECTION varchar(32) NO
  53. DATABASE_COLLATION varchar(32) NO
  54. SHOW CREATE TABLE information_schema.ROUTINES;
  55. Table Create Table
  56. ROUTINES CREATE TEMPORARY TABLE `ROUTINES` (
  57. `SPECIFIC_NAME` varchar(64) NOT NULL DEFAULT '',
  58. `ROUTINE_CATALOG` varchar(512) DEFAULT NULL,
  59. `ROUTINE_SCHEMA` varchar(64) NOT NULL DEFAULT '',
  60. `ROUTINE_NAME` varchar(64) NOT NULL DEFAULT '',
  61. `ROUTINE_TYPE` varchar(9) NOT NULL DEFAULT '',
  62. `DTD_IDENTIFIER` varchar(64) DEFAULT NULL,
  63. `ROUTINE_BODY` varchar(8) NOT NULL DEFAULT '',
  64. `ROUTINE_DEFINITION` longtext,
  65. `EXTERNAL_NAME` varchar(64) DEFAULT NULL,
  66. `EXTERNAL_LANGUAGE` varchar(64) DEFAULT NULL,
  67. `PARAMETER_STYLE` varchar(8) NOT NULL DEFAULT '',
  68. `IS_DETERMINISTIC` varchar(3) NOT NULL DEFAULT '',
  69. `SQL_DATA_ACCESS` varchar(64) NOT NULL DEFAULT '',
  70. `SQL_PATH` varchar(64) DEFAULT NULL,
  71. `SECURITY_TYPE` varchar(7) NOT NULL DEFAULT '',
  72. `CREATED` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  73. `LAST_ALTERED` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  74. `SQL_MODE` varchar(8192) NOT NULL DEFAULT '',
  75. `ROUTINE_COMMENT` varchar(64) NOT NULL DEFAULT '',
  76. `DEFINER` varchar(77) NOT NULL DEFAULT '',
  77. `CHARACTER_SET_CLIENT` varchar(32) NOT NULL DEFAULT '',
  78. `COLLATION_CONNECTION` varchar(32) NOT NULL DEFAULT '',
  79. `DATABASE_COLLATION` varchar(32) NOT NULL DEFAULT ''
  80. ) ENGINE=MyISAM DEFAULT CHARSET=utf8
  81. SHOW COLUMNS FROM information_schema.ROUTINES;
  82. Field Type Null Key Default Extra
  83. SPECIFIC_NAME varchar(64) NO
  84. ROUTINE_CATALOG varchar(512) YES NULL
  85. ROUTINE_SCHEMA varchar(64) NO
  86. ROUTINE_NAME varchar(64) NO
  87. ROUTINE_TYPE varchar(9) NO
  88. DTD_IDENTIFIER varchar(64) YES NULL
  89. ROUTINE_BODY varchar(8) NO
  90. ROUTINE_DEFINITION longtext YES NULL
  91. EXTERNAL_NAME varchar(64) YES NULL
  92. EXTERNAL_LANGUAGE varchar(64) YES NULL
  93. PARAMETER_STYLE varchar(8) NO
  94. IS_DETERMINISTIC varchar(3) NO
  95. SQL_DATA_ACCESS varchar(64) NO
  96. SQL_PATH varchar(64) YES NULL
  97. SECURITY_TYPE varchar(7) NO
  98. CREATED datetime NO 0000-00-00 00:00:00
  99. LAST_ALTERED datetime NO 0000-00-00 00:00:00
  100. SQL_MODE varchar(8192) NO
  101. ROUTINE_COMMENT varchar(64) NO
  102. DEFINER varchar(77) NO
  103. CHARACTER_SET_CLIENT varchar(32) NO
  104. COLLATION_CONNECTION varchar(32) NO
  105. DATABASE_COLLATION varchar(32) NO
  106. USE test;
  107. DROP PROCEDURE IF EXISTS sp_for_routines;
  108. DROP FUNCTION IF EXISTS function_for_routines;
  109. CREATE PROCEDURE sp_for_routines() SELECT 'db_datadict';
  110. CREATE FUNCTION function_for_routines() RETURNS INT RETURN 0;
  111. SELECT specific_name,routine_catalog,routine_schema,routine_name,routine_type,
  112. routine_body,external_name,external_language,parameter_style,sql_path
  113. FROM information_schema.routines
  114. WHERE routine_catalog IS NOT NULL OR external_name IS NOT NULL
  115. OR external_language IS NOT NULL OR sql_path IS NOT NULL
  116. OR routine_body <> 'SQL' OR parameter_style <> 'SQL'
  117. OR specific_name <> routine_name;
  118. specific_name routine_catalog routine_schema routine_name routine_type routine_body external_name external_language parameter_style sql_path
  119. DROP PROCEDURE sp_for_routines;
  120. DROP FUNCTION function_for_routines;
  121. ################################################################################
  122. # Testcase 3.2.8.2 + 3.2.8.3: INFORMATION_SCHEMA.ROUTINES accessible information
  123. ################################################################################
  124. DROP DATABASE IF EXISTS db_datadict;
  125. DROP DATABASE IF EXISTS db_datadict_2;
  126. CREATE DATABASE db_datadict;
  127. USE db_datadict;
  128. CREATE TABLE res_6_408002_1(f1 CHAR(3), f2 TEXT(25), f3 DATE, f4 INT)
  129. ENGINE = <other_engine_type>;
  130. INSERT INTO res_6_408002_1(f1, f2, f3, f4)
  131. VALUES('abc', 'xyz', '1989-11-09', 0815);
  132. DROP PROCEDURE IF EXISTS sp_6_408002_1;
  133. CREATE PROCEDURE sp_6_408002_1()
  134. BEGIN
  135. SELECT * FROM db_datadict.res_6_408002_1;
  136. END//
  137. CREATE DATABASE db_datadict_2;
  138. USE db_datadict_2;
  139. CREATE TABLE res_6_408002_2(f1 CHAR(3), f2 TEXT(25), f3 DATE, f4 INT)
  140. ENGINE = <other_engine_type>;
  141. INSERT INTO res_6_408002_2(f1, f2, f3, f4)
  142. VALUES('abc', 'xyz', '1990-10-03', 4711);
  143. DROP PROCEDURE IF EXISTS sp_6_408002_2;
  144. CREATE PROCEDURE sp_6_408002_2()
  145. BEGIN
  146. SELECT * FROM db_datadict_2.res_6_408002_2;
  147. END//
  148. DROP USER 'testuser1'@'localhost';
  149. CREATE USER 'testuser1'@'localhost';
  150. DROP USER 'testuser2'@'localhost';
  151. CREATE USER 'testuser2'@'localhost';
  152. DROP USER 'testuser3'@'localhost';
  153. CREATE USER 'testuser3'@'localhost';
  154. GRANT SELECT ON db_datadict_2.* TO 'testuser1'@'localhost';
  155. GRANT EXECUTE ON db_datadict_2.* TO 'testuser1'@'localhost';
  156. GRANT EXECUTE ON db_datadict.* TO 'testuser1'@'localhost';
  157. GRANT SELECT ON db_datadict.* TO 'testuser2'@'localhost';
  158. GRANT EXECUTE ON PROCEDURE db_datadict_2.sp_6_408002_2
  159. TO 'testuser2'@'localhost';
  160. GRANT EXECUTE ON db_datadict_2.* TO 'testuser2'@'localhost';
  161. FLUSH PRIVILEGES;
  162. # Establish connection testuser1 (user=testuser1)
  163. SELECT * FROM information_schema.routines;
  164. SPECIFIC_NAME ROUTINE_CATALOG ROUTINE_SCHEMA ROUTINE_NAME ROUTINE_TYPE DTD_IDENTIFIER ROUTINE_BODY ROUTINE_DEFINITION EXTERNAL_NAME EXTERNAL_LANGUAGE PARAMETER_STYLE IS_DETERMINISTIC SQL_DATA_ACCESS SQL_PATH SECURITY_TYPE CREATED LAST_ALTERED SQL_MODE ROUTINE_COMMENT DEFINER CHARACTER_SET_CLIENT COLLATION_CONNECTION DATABASE_COLLATION
  165. sp_6_408002_1 NULL db_datadict sp_6_408002_1 PROCEDURE NULL SQL NULL NULL NULL SQL NO CONTAINS SQL NULL DEFINER YYYY-MM-DD hh:mm:ss YYYY-MM-DD hh:mm:ss root@localhost latin1 latin1_swedish_ci latin1_swedish_ci
  166. sp_6_408002_2 NULL db_datadict_2 sp_6_408002_2 PROCEDURE NULL SQL NULL NULL NULL SQL NO CONTAINS SQL NULL DEFINER YYYY-MM-DD hh:mm:ss YYYY-MM-DD hh:mm:ss root@localhost latin1 latin1_swedish_ci latin1_swedish_ci
  167. # Establish connection testuser2 (user=testuser2)
  168. SELECT * FROM information_schema.routines;
  169. SPECIFIC_NAME ROUTINE_CATALOG ROUTINE_SCHEMA ROUTINE_NAME ROUTINE_TYPE DTD_IDENTIFIER ROUTINE_BODY ROUTINE_DEFINITION EXTERNAL_NAME EXTERNAL_LANGUAGE PARAMETER_STYLE IS_DETERMINISTIC SQL_DATA_ACCESS SQL_PATH SECURITY_TYPE CREATED LAST_ALTERED SQL_MODE ROUTINE_COMMENT DEFINER CHARACTER_SET_CLIENT COLLATION_CONNECTION DATABASE_COLLATION
  170. sp_6_408002_2 NULL db_datadict_2 sp_6_408002_2 PROCEDURE NULL SQL NULL NULL NULL SQL NO CONTAINS SQL NULL DEFINER YYYY-MM-DD hh:mm:ss YYYY-MM-DD hh:mm:ss root@localhost latin1 latin1_swedish_ci latin1_swedish_ci
  171. # Establish connection testuser3 (user=testuser3)
  172. SELECT * FROM information_schema.routines;
  173. SPECIFIC_NAME ROUTINE_CATALOG ROUTINE_SCHEMA ROUTINE_NAME ROUTINE_TYPE DTD_IDENTIFIER ROUTINE_BODY ROUTINE_DEFINITION EXTERNAL_NAME EXTERNAL_LANGUAGE PARAMETER_STYLE IS_DETERMINISTIC SQL_DATA_ACCESS SQL_PATH SECURITY_TYPE CREATED LAST_ALTERED SQL_MODE ROUTINE_COMMENT DEFINER CHARACTER_SET_CLIENT COLLATION_CONNECTION DATABASE_COLLATION
  174. # Switch to connection default and close connections testuser1,testuser2,testuser3
  175. DROP USER 'testuser1'@'localhost';
  176. DROP USER 'testuser2'@'localhost';
  177. DROP USER 'testuser3'@'localhost';
  178. USE test;
  179. DROP DATABASE db_datadict;
  180. DROP DATABASE db_datadict_2;
  181. #########################################################################
  182. # 3.2.1.13+3.2.1.14+3.2.1.15: INFORMATION_SCHEMA.ROUTINES modifications
  183. #########################################################################
  184. DROP DATABASE IF EXISTS db_datadict;
  185. CREATE DATABASE db_datadict;
  186. SELECT * FROM information_schema.routines WHERE routine_schema = 'db_datadict';
  187. SPECIFIC_NAME ROUTINE_CATALOG ROUTINE_SCHEMA ROUTINE_NAME ROUTINE_TYPE DTD_IDENTIFIER ROUTINE_BODY ROUTINE_DEFINITION EXTERNAL_NAME EXTERNAL_LANGUAGE PARAMETER_STYLE IS_DETERMINISTIC SQL_DATA_ACCESS SQL_PATH SECURITY_TYPE CREATED LAST_ALTERED SQL_MODE ROUTINE_COMMENT DEFINER CHARACTER_SET_CLIENT COLLATION_CONNECTION DATABASE_COLLATION
  188. USE db_datadict;
  189. CREATE PROCEDURE sp_for_routines() SELECT 'db_datadict';
  190. CREATE FUNCTION function_for_routines() RETURNS INT RETURN 0;
  191. SELECT * FROM information_schema.routines WHERE routine_schema = 'db_datadict'
  192. ORDER BY routine_name;
  193. SPECIFIC_NAME function_for_routines
  194. ROUTINE_CATALOG NULL
  195. ROUTINE_SCHEMA db_datadict
  196. ROUTINE_NAME function_for_routines
  197. ROUTINE_TYPE FUNCTION
  198. DTD_IDENTIFIER int(11)
  199. ROUTINE_BODY SQL
  200. ROUTINE_DEFINITION RETURN 0
  201. EXTERNAL_NAME NULL
  202. EXTERNAL_LANGUAGE NULL
  203. PARAMETER_STYLE SQL
  204. IS_DETERMINISTIC NO
  205. SQL_DATA_ACCESS CONTAINS SQL
  206. SQL_PATH NULL
  207. SECURITY_TYPE DEFINER
  208. CREATED <created>
  209. LAST_ALTERED <modified>
  210. SQL_MODE
  211. ROUTINE_COMMENT
  212. DEFINER root@localhost
  213. CHARACTER_SET_CLIENT latin1
  214. COLLATION_CONNECTION latin1_swedish_ci
  215. DATABASE_COLLATION latin1_swedish_ci
  216. SPECIFIC_NAME sp_for_routines
  217. ROUTINE_CATALOG NULL
  218. ROUTINE_SCHEMA db_datadict
  219. ROUTINE_NAME sp_for_routines
  220. ROUTINE_TYPE PROCEDURE
  221. DTD_IDENTIFIER NULL
  222. ROUTINE_BODY SQL
  223. ROUTINE_DEFINITION SELECT 'db_datadict'
  224. EXTERNAL_NAME NULL
  225. EXTERNAL_LANGUAGE NULL
  226. PARAMETER_STYLE SQL
  227. IS_DETERMINISTIC NO
  228. SQL_DATA_ACCESS CONTAINS SQL
  229. SQL_PATH NULL
  230. SECURITY_TYPE DEFINER
  231. CREATED <created>
  232. LAST_ALTERED <modified>
  233. SQL_MODE
  234. ROUTINE_COMMENT
  235. DEFINER root@localhost
  236. CHARACTER_SET_CLIENT latin1
  237. COLLATION_CONNECTION latin1_swedish_ci
  238. DATABASE_COLLATION latin1_swedish_ci
  239. ALTER PROCEDURE sp_for_routines SQL SECURITY INVOKER;
  240. ALTER FUNCTION function_for_routines COMMENT 'updated comments';
  241. SELECT * FROM information_schema.routines WHERE routine_schema = 'db_datadict'
  242. ORDER BY routine_name;
  243. SPECIFIC_NAME function_for_routines
  244. ROUTINE_CATALOG NULL
  245. ROUTINE_SCHEMA db_datadict
  246. ROUTINE_NAME function_for_routines
  247. ROUTINE_TYPE FUNCTION
  248. DTD_IDENTIFIER int(11)
  249. ROUTINE_BODY SQL
  250. ROUTINE_DEFINITION RETURN 0
  251. EXTERNAL_NAME NULL
  252. EXTERNAL_LANGUAGE NULL
  253. PARAMETER_STYLE SQL
  254. IS_DETERMINISTIC NO
  255. SQL_DATA_ACCESS CONTAINS SQL
  256. SQL_PATH NULL
  257. SECURITY_TYPE DEFINER
  258. CREATED <created>
  259. LAST_ALTERED <modified>
  260. SQL_MODE
  261. ROUTINE_COMMENT updated comments
  262. DEFINER root@localhost
  263. CHARACTER_SET_CLIENT latin1
  264. COLLATION_CONNECTION latin1_swedish_ci
  265. DATABASE_COLLATION latin1_swedish_ci
  266. SPECIFIC_NAME sp_for_routines
  267. ROUTINE_CATALOG NULL
  268. ROUTINE_SCHEMA db_datadict
  269. ROUTINE_NAME sp_for_routines
  270. ROUTINE_TYPE PROCEDURE
  271. DTD_IDENTIFIER NULL
  272. ROUTINE_BODY SQL
  273. ROUTINE_DEFINITION SELECT 'db_datadict'
  274. EXTERNAL_NAME NULL
  275. EXTERNAL_LANGUAGE NULL
  276. PARAMETER_STYLE SQL
  277. IS_DETERMINISTIC NO
  278. SQL_DATA_ACCESS CONTAINS SQL
  279. SQL_PATH NULL
  280. SECURITY_TYPE INVOKER
  281. CREATED <created>
  282. LAST_ALTERED <modified>
  283. SQL_MODE
  284. ROUTINE_COMMENT
  285. DEFINER root@localhost
  286. CHARACTER_SET_CLIENT latin1
  287. COLLATION_CONNECTION latin1_swedish_ci
  288. DATABASE_COLLATION latin1_swedish_ci
  289. DROP PROCEDURE sp_for_routines;
  290. DROP FUNCTION function_for_routines;
  291. SELECT * FROM information_schema.routines WHERE routine_schema = 'db_datadict';
  292. SPECIFIC_NAME ROUTINE_CATALOG ROUTINE_SCHEMA ROUTINE_NAME ROUTINE_TYPE DTD_IDENTIFIER ROUTINE_BODY ROUTINE_DEFINITION EXTERNAL_NAME EXTERNAL_LANGUAGE PARAMETER_STYLE IS_DETERMINISTIC SQL_DATA_ACCESS SQL_PATH SECURITY_TYPE CREATED LAST_ALTERED SQL_MODE ROUTINE_COMMENT DEFINER CHARACTER_SET_CLIENT COLLATION_CONNECTION DATABASE_COLLATION
  293. CREATE PROCEDURE sp_for_routines() SELECT 'db_datadict';
  294. CREATE FUNCTION function_for_routines() RETURNS INT RETURN 0;
  295. SELECT * FROM information_schema.routines WHERE routine_schema = 'db_datadict'
  296. ORDER BY routine_name;
  297. SPECIFIC_NAME function_for_routines
  298. ROUTINE_CATALOG NULL
  299. ROUTINE_SCHEMA db_datadict
  300. ROUTINE_NAME function_for_routines
  301. ROUTINE_TYPE FUNCTION
  302. DTD_IDENTIFIER int(11)
  303. ROUTINE_BODY SQL
  304. ROUTINE_DEFINITION RETURN 0
  305. EXTERNAL_NAME NULL
  306. EXTERNAL_LANGUAGE NULL
  307. PARAMETER_STYLE SQL
  308. IS_DETERMINISTIC NO
  309. SQL_DATA_ACCESS CONTAINS SQL
  310. SQL_PATH NULL
  311. SECURITY_TYPE DEFINER
  312. CREATED <created>
  313. LAST_ALTERED <modified>
  314. SQL_MODE
  315. ROUTINE_COMMENT
  316. DEFINER root@localhost
  317. CHARACTER_SET_CLIENT latin1
  318. COLLATION_CONNECTION latin1_swedish_ci
  319. DATABASE_COLLATION latin1_swedish_ci
  320. SPECIFIC_NAME sp_for_routines
  321. ROUTINE_CATALOG NULL
  322. ROUTINE_SCHEMA db_datadict
  323. ROUTINE_NAME sp_for_routines
  324. ROUTINE_TYPE PROCEDURE
  325. DTD_IDENTIFIER NULL
  326. ROUTINE_BODY SQL
  327. ROUTINE_DEFINITION SELECT 'db_datadict'
  328. EXTERNAL_NAME NULL
  329. EXTERNAL_LANGUAGE NULL
  330. PARAMETER_STYLE SQL
  331. IS_DETERMINISTIC NO
  332. SQL_DATA_ACCESS CONTAINS SQL
  333. SQL_PATH NULL
  334. SECURITY_TYPE DEFINER
  335. CREATED <created>
  336. LAST_ALTERED <modified>
  337. SQL_MODE
  338. ROUTINE_COMMENT
  339. DEFINER root@localhost
  340. CHARACTER_SET_CLIENT latin1
  341. COLLATION_CONNECTION latin1_swedish_ci
  342. DATABASE_COLLATION latin1_swedish_ci
  343. use test;
  344. DROP DATABASE db_datadict;
  345. SELECT * FROM information_schema.routines WHERE routine_schema = 'db_datadict';
  346. SPECIFIC_NAME ROUTINE_CATALOG ROUTINE_SCHEMA ROUTINE_NAME ROUTINE_TYPE DTD_IDENTIFIER ROUTINE_BODY ROUTINE_DEFINITION EXTERNAL_NAME EXTERNAL_LANGUAGE PARAMETER_STYLE IS_DETERMINISTIC SQL_DATA_ACCESS SQL_PATH SECURITY_TYPE CREATED LAST_ALTERED SQL_MODE ROUTINE_COMMENT DEFINER CHARACTER_SET_CLIENT COLLATION_CONNECTION DATABASE_COLLATION
  347. #########################################################################
  348. # 3.2.8.4: INFORMATION_SCHEMA.ROUTINES routine body too big for
  349. # ROUTINE_DEFINITION column
  350. #########################################################################
  351. DROP DATABASE IF EXISTS db_datadict;
  352. CREATE DATABASE db_datadict;
  353. USE db_datadict;
  354. CREATE TABLE db_datadict.res_6_408004_1
  355. (f1 LONGTEXT , f2 MEDIUMINT , f3 LONGBLOB , f4 REAL , f5 YEAR)
  356. ENGINE = <other_engine_type>;
  357. INSERT INTO db_datadict.res_6_408004_1
  358. VALUES ('abc', 98765 , 99999999 , 98765, 10);
  359. CREATE TABLE db_datadict.res_6_408004_2
  360. (f1 LONGTEXT , f2 MEDIUMINT , f3 LONGBLOB , f4 REAL , f5 YEAR)
  361. ENGINE = <other_engine_type>;
  362. INSERT INTO db_datadict.res_6_408004_2
  363. VALUES ('abc', 98765 , 99999999 , 98765, 10);
  364. # Checking the max. possible length of (currently) 4 GByte is not
  365. # in this environment here.
  366. CREATE PROCEDURE sp_6_408004 ()
  367. BEGIN
  368. DECLARE done INTEGER DEFAULt 0;
  369. DECLARE variable_number_1 LONGTEXT;
  370. DECLARE variable_number_2 MEDIUMINT;
  371. DECLARE variable_number_3 LONGBLOB;
  372. DECLARE variable_number_4 REAL;
  373. DECLARE variable_number_5 YEAR;
  374. DECLARE cursor_number_1 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  375. DECLARE cursor_number_2 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  376. DECLARE cursor_number_3 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  377. DECLARE cursor_number_4 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  378. DECLARE cursor_number_5 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  379. DECLARE CONTINUE HANDLER FOR SQLSTATE '02000' SET done = 1;
  380. BEGIN
  381. OPEN cursor_number_1;
  382. WHILE done <> 1 DO
  383. FETCH cursor_number_1
  384. INTO variable_number_1, variable_number_2, variable_number_3,
  385. variable_number_4, variable_number_5;
  386. IF done <> 0 THEN
  387. INSERT INTO res_6_408004_2
  388. VALUES (variable_number_1, variable_number_2, variable_number_3,
  389. variable_number_4, variable_number_5);
  390. END IF;
  391. END WHILE;
  392. BEGIN
  393. BEGIN
  394. SET done = 0;
  395. OPEN cursor_number_2;
  396. WHILE done <> 1 DO
  397. FETCH cursor_number_2
  398. INTO variable_number_1, variable_number_2, variable_number_3,
  399. variable_number_4, variable_number_5;
  400. IF done <> 0 THEN
  401. INSERT INTO res_6_408004_2
  402. VALUES(variable_number_1, variable_number_2, variable_number_3,
  403. variable_number_4, variable_number_5);
  404. END IF;
  405. END WHILE;
  406. END;
  407. SET done = 0;
  408. OPEN cursor_number_3;
  409. WHILE done <> 1 DO
  410. FETCH cursor_number_3
  411. INTO variable_number_1, variable_number_2, variable_number_3,
  412. variable_number_4, variable_number_5;
  413. IF done <> 0 THEN
  414. INSERT INTO res_6_408004_2
  415. VALUES(variable_number_1, variable_number_2, variable_number_3,
  416. variable_number_4, variable_number_5);
  417. END IF;
  418. END WHILE;
  419. END;
  420. END;
  421. BEGIN
  422. SET done = 0;
  423. OPEN cursor_number_4;
  424. WHILE done <> 1 DO
  425. FETCH cursor_number_4
  426. INTO variable_number_1, variable_number_2, variable_number_3,
  427. variable_number_4, variable_number_5;
  428. IF done <> 0 THEN
  429. INSERT INTO res_6_408004_2
  430. VALUES (variable_number_1, variable_number_2, variable_number_3,
  431. variable_number_4, variable_number_5);
  432. END IF;
  433. END WHILE;
  434. END;
  435. BEGIN
  436. SET @a='test row';
  437. SELECT @a;
  438. SELECT @a;
  439. SELECT @a;
  440. END;
  441. BEGIN
  442. SET done = 0;
  443. OPEN cursor_number_5;
  444. WHILE done <> 1 DO
  445. FETCH cursor_number_5
  446. INTO variable_number_1, variable_number_2, variable_number_3,
  447. variable_number_4, variable_number_5;
  448. IF done <> 0 THEN
  449. INSERT INTO res_6_408004_2
  450. VALUES (variable_number_1, variable_number_2, variable_number_3,
  451. variable_number_4, variable_number_5);
  452. END IF;
  453. END WHILE;
  454. END;
  455. BEGIN
  456. SET @a='test row';
  457. SELECT @a;
  458. SELECT @a;
  459. SELECT @a;
  460. END;
  461. END//
  462. CALL db_datadict.sp_6_408004 ();
  463. @a
  464. test row
  465. @a
  466. test row
  467. @a
  468. test row
  469. @a
  470. test row
  471. @a
  472. test row
  473. @a
  474. test row
  475. SELECT * FROM db_datadict.res_6_408004_2;
  476. f1 f2 f3 f4 f5
  477. abc 98765 99999999 98765 2010
  478. abc 98765 99999999 98765 2010
  479. abc 98765 99999999 98765 2010
  480. abc 98765 99999999 98765 2010
  481. abc 98765 99999999 98765 2010
  482. abc 98765 99999999 98765 2010
  483. SELECT *, LENGTH(routine_definition) FROM information_schema.routines
  484. WHERE routine_schema = 'db_datadict';
  485. SPECIFIC_NAME sp_6_408004
  486. ROUTINE_CATALOG NULL
  487. ROUTINE_SCHEMA db_datadict
  488. ROUTINE_NAME sp_6_408004
  489. ROUTINE_TYPE PROCEDURE
  490. DTD_IDENTIFIER NULL
  491. ROUTINE_BODY SQL
  492. ROUTINE_DEFINITION BEGIN
  493. DECLARE done INTEGER DEFAULt 0;
  494. DECLARE variable_number_1 LONGTEXT;
  495. DECLARE variable_number_2 MEDIUMINT;
  496. DECLARE variable_number_3 LONGBLOB;
  497. DECLARE variable_number_4 REAL;
  498. DECLARE variable_number_5 YEAR;
  499. DECLARE cursor_number_1 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  500. DECLARE cursor_number_2 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  501. DECLARE cursor_number_3 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  502. DECLARE cursor_number_4 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  503. DECLARE cursor_number_5 CURSOR FOR SELECT * FROM res_6_408004_1 LIMIT 0, 10;
  504. DECLARE CONTINUE HANDLER FOR SQLSTATE '02000' SET done = 1;
  505. BEGIN
  506. OPEN cursor_number_1;
  507. WHILE done <> 1 DO
  508. FETCH cursor_number_1
  509. INTO variable_number_1, variable_number_2, variable_number_3,
  510. variable_number_4, variable_number_5;
  511. IF done <> 0 THEN
  512. INSERT INTO res_6_408004_2
  513. VALUES (variable_number_1, variable_number_2, variable_number_3,
  514. variable_number_4, variable_number_5);
  515. END IF;
  516. END WHILE;
  517. BEGIN
  518. BEGIN
  519. SET done = 0;
  520. OPEN cursor_number_2;
  521. WHILE done <> 1 DO
  522. FETCH cursor_number_2
  523. INTO variable_number_1, variable_number_2, variable_number_3,
  524. variable_number_4, variable_number_5;
  525. IF done <> 0 THEN
  526. INSERT INTO res_6_408004_2
  527. VALUES(variable_number_1, variable_number_2, variable_number_3,
  528. variable_number_4, variable_number_5);
  529. END IF;
  530. END WHILE;
  531. END;
  532. SET done = 0;
  533. OPEN cursor_number_3;
  534. WHILE done <> 1 DO
  535. FETCH cursor_number_3
  536. INTO variable_number_1, variable_number_2, variable_number_3,
  537. variable_number_4, variable_number_5;
  538. IF done <> 0 THEN
  539. INSERT INTO res_6_408004_2
  540. VALUES(variable_number_1, variable_number_2, variable_number_3,
  541. variable_number_4, variable_number_5);
  542. END IF;
  543. END WHILE;
  544. END;
  545. END;
  546. BEGIN
  547. SET done = 0;
  548. OPEN cursor_number_4;
  549. WHILE done <> 1 DO
  550. FETCH cursor_number_4
  551. INTO variable_number_1, variable_number_2, variable_number_3,
  552. variable_number_4, variable_number_5;
  553. IF done <> 0 THEN
  554. INSERT INTO res_6_408004_2
  555. VALUES (variable_number_1, variable_number_2, variable_number_3,
  556. variable_number_4, variable_number_5);
  557. END IF;
  558. END WHILE;
  559. END;
  560. BEGIN
  561. SET @a='test row';
  562. SELECT @a;
  563. SELECT @a;
  564. SELECT @a;
  565. END;
  566. BEGIN
  567. SET done = 0;
  568. OPEN cursor_number_5;
  569. WHILE done <> 1 DO
  570. FETCH cursor_number_5
  571. INTO variable_number_1, variable_number_2, variable_number_3,
  572. variable_number_4, variable_number_5;
  573. IF done <> 0 THEN
  574. INSERT INTO res_6_408004_2
  575. VALUES (variable_number_1, variable_number_2, variable_number_3,
  576. variable_number_4, variable_number_5);
  577. END IF;
  578. END WHILE;
  579. END;
  580. BEGIN
  581. SET @a='test row';
  582. SELECT @a;
  583. SELECT @a;
  584. SELECT @a;
  585. END;
  586. END
  587. EXTERNAL_NAME NULL
  588. EXTERNAL_LANGUAGE NULL
  589. PARAMETER_STYLE SQL
  590. IS_DETERMINISTIC NO
  591. SQL_DATA_ACCESS CONTAINS SQL
  592. SQL_PATH NULL
  593. SECURITY_TYPE DEFINER
  594. CREATED YYYY-MM-DD hh:mm:ss
  595. LAST_ALTERED YYYY-MM-DD hh:mm:ss
  596. SQL_MODE
  597. ROUTINE_COMMENT
  598. DEFINER root@localhost
  599. CHARACTER_SET_CLIENT latin1
  600. COLLATION_CONNECTION latin1_swedish_ci
  601. DATABASE_COLLATION latin1_swedish_ci
  602. LENGTH(routine_definition) 2549
  603. DROP DATABASE db_datadict;
  604. ########################################################################
  605. # Testcases 3.2.1.3-3.2.1.5 + 3.2.1.8-3.2.1.12: INSERT/UPDATE/DELETE and
  606. # DDL on INFORMATION_SCHEMA table are not supported
  607. ########################################################################
  608. DROP DATABASE IF EXISTS db_datadict;
  609. CREATE DATABASE db_datadict;
  610. USE db_datadict;
  611. CREATE PROCEDURE sp_for_routines() SELECT 'db_datadict';
  612. USE test;
  613. INSERT INTO information_schema.routines (routine_name, routine_type )
  614. VALUES ('p2', 'procedure');
  615. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  616. UPDATE information_schema.routines SET routine_name = 'p2'
  617. WHERE routine_body = 'sql';
  618. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  619. DELETE FROM information_schema.routines ;
  620. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  621. TRUNCATE information_schema.routines ;
  622. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  623. CREATE INDEX i7 ON information_schema.routines (routine_name);
  624. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  625. ALTER TABLE information_schema.routines ADD f1 INT;
  626. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  627. ALTER TABLE information_schema.routines DISCARD TABLESPACE;
  628. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  629. DROP TABLE information_schema.routines ;
  630. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  631. ALTER TABLE information_schema.routines RENAME db_datadict.routines;
  632. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  633. ALTER TABLE information_schema.routines RENAME information_schema.xroutines;
  634. ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
  635. DROP DATABASE db_datadict;