mariadb/mysql-test/suite/perfschema/r/ddl_setup_consumers.result

alter table performance_schema.setup_consumers add column foo integer;
ERROR 42000: Access denied for user 'root'@'localhost' to database 'performance_schema'
truncate table performance_schema.setup_consumers;
ERROR HY000: Invalid performance_schema usage.
ALTER TABLE performance_schema.setup_consumers ADD INDEX test_index(NAME);
ERROR 42000: Access denied for user 'root'@'localhost' to database 'performance_schema'
CREATE UNIQUE INDEX test_index ON performance_schema.setup_consumers(NAME);
ERROR 42000: Access denied for user 'root'@'localhost' to database 'performance_schema'
Bug#57609 performance_schema does not work with lower_case_table_names Before this fix, the performance schema tables were defined in UPPERCASE. This was incompatible with the lowercase_table_names option, and caused issues with the install / upgrade process, when changing the lower case table names setting after the install or upgrade. With this fix, all performance schema tables are exposed with lowercase names. As a result, the name of the performance schema table is always lowercase, no matter how / if / when the lowercase_table_names setting if changed. 2010-11-03 16:42:33 +01:00			`alter table performance_schema.setup_consumers add column foo integer;`
WL#2360 Performance schema Part V: performance schema implementation 2010-01-11 18:47:27 -07:00			`ERROR 42000: Access denied for user 'root'@'localhost' to database 'performance_schema'`
Bug#57609 performance_schema does not work with lower_case_table_names Before this fix, the performance schema tables were defined in UPPERCASE. This was incompatible with the lowercase_table_names option, and caused issues with the install / upgrade process, when changing the lower case table names setting after the install or upgrade. With this fix, all performance schema tables are exposed with lowercase names. As a result, the name of the performance schema table is always lowercase, no matter how / if / when the lowercase_table_names setting if changed. 2010-11-03 16:42:33 +01:00			`truncate table performance_schema.setup_consumers;`
WL#2360 Performance schema Part V: performance schema implementation 2010-01-11 18:47:27 -07:00			`ERROR HY000: Invalid performance_schema usage.`
Bug#57609 performance_schema does not work with lower_case_table_names Before this fix, the performance schema tables were defined in UPPERCASE. This was incompatible with the lowercase_table_names option, and caused issues with the install / upgrade process, when changing the lower case table names setting after the install or upgrade. With this fix, all performance schema tables are exposed with lowercase names. As a result, the name of the performance schema table is always lowercase, no matter how / if / when the lowercase_table_names setting if changed. 2010-11-03 16:42:33 +01:00			`ALTER TABLE performance_schema.setup_consumers ADD INDEX test_index(NAME);`
WL#2360 Performance schema Part V: performance schema implementation 2010-01-11 18:47:27 -07:00			`ERROR 42000: Access denied for user 'root'@'localhost' to database 'performance_schema'`
Bug#57609 performance_schema does not work with lower_case_table_names Before this fix, the performance schema tables were defined in UPPERCASE. This was incompatible with the lowercase_table_names option, and caused issues with the install / upgrade process, when changing the lower case table names setting after the install or upgrade. With this fix, all performance schema tables are exposed with lowercase names. As a result, the name of the performance schema table is always lowercase, no matter how / if / when the lowercase_table_names setting if changed. 2010-11-03 16:42:33 +01:00			`CREATE UNIQUE INDEX test_index ON performance_schema.setup_consumers(NAME);`
WL#2360 Performance schema Part V: performance schema implementation 2010-01-11 18:47:27 -07:00			`ERROR 42000: Access denied for user 'root'@'localhost' to database 'performance_schema'`