mariadb/mysql-test/r/information_schema_db.result

use INFORMATION_SCHEMA;
show tables;
Tables_in_information_schema
CHARACTER_SETS
COLLATIONS
COLLATION_CHARACTER_SET_APPLICABILITY
COLUMNS
COLUMN_PRIVILEGES
ENGINES
EVENTS
FILES
KEY_COLUMN_USAGE
PARTITIONS
PLUGINS
PROCESSLIST
ROUTINES
SCHEMATA
SCHEMA_PRIVILEGES
STATISTICS
TABLES
TABLE_CONSTRAINTS
TABLE_PRIVILEGES
TRIGGERS
USER_PRIVILEGES
VIEWS
show tables from INFORMATION_SCHEMA like 'T%';
Tables_in_information_schema (T%)
TABLES
TABLE_CONSTRAINTS
TABLE_PRIVILEGES
TRIGGERS
create database `inf%`;
use `inf%`;
show tables;
Tables_in_inf%
grant all privileges on `inf%`.* to 'mysqltest_1'@'localhost';
create table t1 (f1 int);
create function func1(curr_int int) returns int
begin
declare ret_val int;
select max(f1) from t1 into ret_val;
return ret_val;
end|
create view v1 as select f1 from t1 where f1 = func1(f1);
select * from information_schema.tables;
drop user mysqltest_1@localhost;
drop view v1;
drop function func1;
drop table t1;
drop database `inf%`;
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			`use INFORMATION_SCHEMA;`
			`show tables;`
Fix for bug #10659: information_schema_db fail on Mac OS 2005-05-24 12:35:23 +02:00			`Tables_in_information_schema`
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			`CHARACTER_SETS`
			`COLLATIONS`
			`COLLATION_CHARACTER_SET_APPLICABILITY`
fix for bug #12315 - SHOW TABLE STATUS FROM `information_schema`; does not sort tablenames 2005-08-05 11:01:29 +02:00			`COLUMNS`
			`COLUMN_PRIVILEGES`
This patch does the following: 1) Fixes breakage in embedded server build for XMLPath push. 2) Hides PARTITION engine from view. 3) Add ENGINES information schema (and it should now be clear from this patch on how to turn any show command into an information schema). 2005-12-22 10:07:47 +01:00			`ENGINES`
fix for bug#16642 (Events: No INFORMATION_SCHEMA.EVENTS table) post-review change - use pointer instead of copy on the stack. WL#1034 (Internal CRON) This patch adds INFORMATION_SCHEMA.EVENTS table with the following format: EVENT_CATALOG - MYSQL_TYPE_STRING (Always NULL) EVENT_SCHEMA - MYSQL_TYPE_STRING (the database) EVENT_NAME - MYSQL_TYPE_STRING (the name) DEFINER - MYSQL_TYPE_STRING (user@host) EVENT_BODY - MYSQL_TYPE_STRING (the body from mysql.event) EVENT_TYPE - MYSQL_TYPE_STRING ("ONE TIME" \| "RECURRING") EXECUTE_AT - MYSQL_TYPE_TIMESTAMP (set for "ONE TIME" otherwise NULL) INTERVAL_VALUE - MYSQL_TYPE_LONG (set for RECURRING otherwise NULL) INTERVAL_FIELD - MYSQL_TYPE_STRING (set for RECURRING otherwise NULL) SQL_MODE - MYSQL_TYPE_STRING (for now NULL) STARTS - MYSQL_TYPE_TIMESTAMP (starts from mysql.event) ENDS - MYSQL_TYPE_TIMESTAMP (ends from mysql.event) STATUS - MYSQL_TYPE_STRING (ENABLED \| DISABLED) ON_COMPLETION - MYSQL_TYPE_STRING (NOT PRESERVE \| PRESERVE) CREATED - MYSQL_TYPE_TIMESTAMP LAST_ALTERED - MYSQL_TYPE_TIMESTAMP LAST_EXECUTED - MYSQL_TYPE_TIMESTAMP EVENT_COMMENT - MYSQL_TYPE_STRING SQL_MODE is NULL for now, because the value is still not stored in mysql.event . Support will be added as a fix for another bug. This patch also adds SHOW [FULL] EVENTS [FROM db] [LIKE pattern] 1. SHOW EVENTS shows always only the events on the same user, because the PK of mysql.event is (definer, db, name) several users may have event with the same name -> no information disclosure. 2. SHOW FULL EVENTS - shows the events (in the current db as SHOW EVENTS) of all users. The user has to have PROCESS privilege, if not then SHOW FULL EVENTS behave like SHOW EVENTS. 3. If [FROM db] is specified then this db is considered. 4. Event names can be filtered with LIKE pattern. SHOW EVENTS returns table with the following columns, which are subset of the data which is returned by SELECT * FROM I_S.EVENTS Db Name Definer Type Execute at Interval value Interval field Starts Ends Status 2006-01-30 13:15:23 +01:00			`EVENTS`
some fixes from review of WL1359. fix up test cases. 2006-02-01 14:47:08 +01:00			`FILES`
fix for bug #12315 - SHOW TABLE STATUS FROM `information_schema`; does not sort tablenames 2005-08-05 11:01:29 +02:00			`KEY_COLUMN_USAGE`
WL#2506: Information Schema tables for PARTITIONing added I_S 'PARTITIONS' table 2006-01-10 16:44:04 +01:00			`PARTITIONS`
Finalize storage engine plugins Give BerkeleyDB savepoints Remove "enum db_type" from most of the code 2005-12-21 19:18:40 +01:00			`PLUGINS`
The patch adds PROCESSLIST information schema 2006-02-16 14:45:05 +01:00			`PROCESSLIST`
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			`ROUTINES`
fix for bug #12315 - SHOW TABLE STATUS FROM `information_schema`; does not sort tablenames 2005-08-05 11:01:29 +02:00			`SCHEMATA`
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			`SCHEMA_PRIVILEGES`
fix for bug #12315 - SHOW TABLE STATUS FROM `information_schema`; does not sort tablenames 2005-08-05 11:01:29 +02:00			`STATISTICS`
			`TABLES`
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			`TABLE_CONSTRAINTS`
fix for bug #12315 - SHOW TABLE STATUS FROM `information_schema`; does not sort tablenames 2005-08-05 11:01:29 +02:00			`TABLE_PRIVILEGES`
Fix for bugs #5892/6182/8751/8758/10994 (based on Antony's patch) "Triggers have the wrong namespace" "Triggers: duplicate names allowed" "Triggers: CREATE TRIGGER does not accept fully qualified names" "SHOW TRIGGERS" 2005-07-19 18:06:49 +02:00			`TRIGGERS`
fix for bug #12315 - SHOW TABLE STATUS FROM `information_schema`; does not sort tablenames 2005-08-05 11:01:29 +02:00			`USER_PRIVILEGES`
information_schema_db.result, information_schema.result: Fix test result. table.h, sql_show.cc: Put I_S tables in lexical order. 2006-01-29 02:44:51 +01:00			`VIEWS`
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			`show tables from INFORMATION_SCHEMA like 'T%';`
Fix for bug #10659: information_schema_db fail on Mac OS 2005-05-24 12:35:23 +02:00			`Tables_in_information_schema (T%)`
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			`TABLES`
			`TABLE_CONSTRAINTS`
fix for bug #12315 - SHOW TABLE STATUS FROM `information_schema`; does not sort tablenames 2005-08-05 11:01:29 +02:00			`TABLE_PRIVILEGES`
Fix for bugs #5892/6182/8751/8758/10994 (based on Antony's patch) "Triggers have the wrong namespace" "Triggers: duplicate names allowed" "Triggers: CREATE TRIGGER does not accept fully qualified names" "SHOW TRIGGERS" 2005-07-19 18:06:49 +02:00			`TRIGGERS`
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			create database `inf%`;
			use `inf%`;
			`show tables;`
			`Tables_in_inf%`
Fix for bug #18113 "SELECT * FROM information_schema.xxx crashes server" Crash happened when one selected data from one of INFORMATION_SCHEMA tables and in order to build its contents server had to open view which used stored function and table or view on which one had not global or database-level privileges (e.g. had only table-level or had no privileges at all). The crash was caused by usage of check_grant() function, which assumes that either number of tables to be inspected by it is limited explicitly or table list used and thd->lex->query_tables_own_last value correspond to each other (the latter should be either 0 or point to next_global member of one of elements of this table list), in conditions when above assumptions were not true. This fix just explicitly limits number of tables to be inspected. Other negative effects which are caused by the fact that thd->lex->query_tables_own_last might not be set properly during processing of I_S tables are less disastrous and will be reported and fixed separetely. 2006-03-20 10:42:02 +01:00			grant all privileges on `inf%`.* to 'mysqltest_1'@'localhost';
			`create table t1 (f1 int);`
			`create function func1(curr_int int) returns int`
			`begin`
			`declare ret_val int;`
			`select max(f1) from t1 into ret_val;`
			`return ret_val;`
			`end\|`
			`create view v1 as select f1 from t1 where f1 = func1(f1);`
			`select * from information_schema.tables;`
			`drop user mysqltest_1@localhost;`
			`drop view v1;`
			`drop function func1;`
			`drop table t1;`
Fix for bug #10018:use INFORMATION_SCHEMA works, but show tables in it returns error 2005-05-06 21:06:10 +02:00			drop database `inf%`;