4 Commits

Author	SHA1	Message	Date
Nikita Malyavin	22e41dae88	MDEV-32501 KEY_PERIOD_USAGE reveals information to unprivileged user ... Restrict access to KEY_PERIOD_USAGE: show the constraint record iff any non-select privilege on any table column is granted. Also drop the unprivileged user in the end of test and add merge anchor.	2024-02-12 22:26:06 +01:00
Nikita Malyavin	5c2f8c017c	MDEV-32503 Queries from I_S.KEY_PERIOD_USAGE do not obey case-sensitivity ... Set the correct values for idx_field1, idx_field2 (i.e. db and table name fields) of ST_SCHEMA_TABLE instance.	2024-02-12 22:26:06 +01:00
Nikita Malyavin	d4b5f7a503	MDEV-32205 crash in get_schema_key_period_usage_record without InnoDB ... Move table open result processing to the caller * st_schema_table::process_table doesn't have to check whether the table was opened successfully * It also doesn't have to check for a thd error and convert it to a warning * This simplifies adding new tables into information_schema * A callback still can output some info to a user in case of error. In order to do this, I_S_EXTENDED_ERROR_HANDLING should be specified in i_s_requested_object.	2024-02-12 22:26:06 +01:00
Nikita Malyavin	4246c0fa01	MDEV-22597 Add views for periods in information_schema ... Two new information_schema views are added: * PERIOD table -- columns TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, PERIOD_NAME, START_COLUMN_NAME, END_COLUMN_NAME. * KEY_PERIOD_USAGE -- works similar to KEY_COLUMN_USAGE, but for periods. Columns CONSTRAINT_CATALOG, CONSTRAINT_SCHEMA, CONSTRAINT_NAME, TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, PERIOD_NAME Two new columns are added to the COLUMNS view: IS_SYSTEM_TIME_PERIOD_START, IS_SYSTEM_TIME_PERIOD_END - contain YES/NO.	2024-02-12 22:26:06 +01:00