mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 02:51:44 +01:00
3a9358a410
This patch introduces a new way of handling UPDATE and DELETE commands at the top level after the parsing phase. This new way of processing update and delete statements can be seen in the implementation of the prepare() and execute() methods from the new Sql_cmd_dml class. This class derived from the Sql_cmd class can be considered as an interface class for processing such commands as SELECT, INSERT, UPDATE, DELETE and other comands manipulating data in tables. With this patch processing of update and delete statements after parsing proceeds by the following schema: - precheck of the access rights is performed for the used tables - the used tables are opened - context analysis phase is performed for the statement - the used tables are locked - the statement is optimized and executed - clean-up is performed for the statement The implementation of the method Sql_cmd_dml::execute() adheres this schema. The virtual functions of the class Sql_cmd_dml used for precheck of the access rights, context analysis, optimization and execution allow to adjust this schema for processing data manipulation statements of any types. This schema of processing data manipulation statements is taken from the current MySQL code. Moreover the definition the class Sql_cmd_dml introduced in this patch is almost a full replica of such class in the existing MySQL. However the implementation of the derived classes for update and delete statements is quite different. This implementation employs the JOIN class for all kinds of update and delete statements. It allows to perform main bulk of context analysis actions by the function JOIN::prepare(). This guarantees that characteristics and properties of the statement tree discovered for optimization phase when doing context analysis are the same for single-table and multi-table updates and deletes. With this patch the following functions are gone: mysql_prepare_update(), mysql_multi_update_prepare(), mysql_update(), mysql_multi_update(), mysql_prepare_delete(), mysql_multi_delete_prepare(), mysql_delete(). The code within these functions have been used as much as possible though. The functions mysql_test_update() and mysql_test_delete() are also not needed anymore. The method Sql_cmd_dml::prepare() serves processing - update/delete statement - PREPARE stmt FROM "<update/delete statement>" - EXECUTE stmt when stmt is prepared from update/delete statement. Approved by Oleksandr Byelkin <sanja@mariadb.com>
90 lines
4.4 KiB
Text
90 lines
4.4 KiB
Text
SHOW TABLES FROM information_schema LIKE 'COLLATIONS';
|
|
Tables_in_information_schema (COLLATIONS)
|
|
COLLATIONS
|
|
#######################################################################
|
|
# Testcase 3.2.1.1: INFORMATION_SCHEMA tables can be queried via SELECT
|
|
#######################################################################
|
|
DROP VIEW IF EXISTS test.v1;
|
|
DROP PROCEDURE IF EXISTS test.p1;
|
|
DROP FUNCTION IF EXISTS test.f1;
|
|
CREATE VIEW test.v1 AS SELECT * FROM information_schema.COLLATIONS;
|
|
CREATE PROCEDURE test.p1() SELECT * FROM information_schema.COLLATIONS;
|
|
CREATE FUNCTION test.f1() returns BIGINT
|
|
BEGIN
|
|
DECLARE counter BIGINT DEFAULT NULL;
|
|
SELECT COUNT(*) INTO counter FROM information_schema.COLLATIONS;
|
|
RETURN counter;
|
|
END//
|
|
# Attention: The printing of the next result sets is disabled.
|
|
SELECT * FROM information_schema.COLLATIONS;
|
|
SELECT * FROM test.v1;
|
|
CALL test.p1;
|
|
SELECT test.f1();
|
|
DROP VIEW test.v1;
|
|
DROP PROCEDURE test.p1;
|
|
DROP FUNCTION test.f1;
|
|
#########################################################################
|
|
# Testcase 3.2.3.1: INFORMATION_SCHEMA.COLLATIONS layout
|
|
#########################################################################
|
|
DESCRIBE information_schema.COLLATIONS;
|
|
Field Type Null Key Default Extra
|
|
COLLATION_NAME varchar(64) NO NULL
|
|
CHARACTER_SET_NAME varchar(32) YES NULL
|
|
ID bigint(11) YES NULL
|
|
IS_DEFAULT varchar(3) YES NULL
|
|
IS_COMPILED varchar(3) NO NULL
|
|
SORTLEN bigint(3) NO NULL
|
|
SHOW CREATE TABLE information_schema.COLLATIONS;
|
|
Table Create Table
|
|
COLLATIONS CREATE TEMPORARY TABLE `COLLATIONS` (
|
|
`COLLATION_NAME` varchar(64) NOT NULL,
|
|
`CHARACTER_SET_NAME` varchar(32),
|
|
`ID` bigint(11),
|
|
`IS_DEFAULT` varchar(3),
|
|
`IS_COMPILED` varchar(3) NOT NULL,
|
|
`SORTLEN` bigint(3) NOT NULL
|
|
) ENGINE=MEMORY DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci
|
|
SHOW COLUMNS FROM information_schema.COLLATIONS;
|
|
Field Type Null Key Default Extra
|
|
COLLATION_NAME varchar(64) NO NULL
|
|
CHARACTER_SET_NAME varchar(32) YES NULL
|
|
ID bigint(11) YES NULL
|
|
IS_DEFAULT varchar(3) YES NULL
|
|
IS_COMPILED varchar(3) NO NULL
|
|
SORTLEN bigint(3) NO NULL
|
|
# Testcases 3.2.3.2 and 3.2.3.3 are checked in suite/funcs_1/t/charset_collation*.test
|
|
########################################################################
|
|
# Testcases 3.2.1.3-3.2.1.5 + 3.2.1.8-3.2.1.12: INSERT/UPDATE/DELETE and
|
|
# DDL on INFORMATION_SCHEMA tables are not supported
|
|
########################################################################
|
|
DROP DATABASE IF EXISTS db_datadict;
|
|
CREATE DATABASE db_datadict;
|
|
INSERT INTO information_schema.collations
|
|
SELECT * FROM information_schema.collations;
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
INSERT INTO information_schema.collations
|
|
(collation_name,character_set_name,id,is_default,is_compiled,sortlen)
|
|
VALUES ( 'cp1251_bin', 'cp1251',50, '', '',0);
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
UPDATE information_schema.collations SET collation_name = 'just updated';
|
|
Got one of the listed errors
|
|
DELETE FROM information_schema.collations WHERE table_name = 't1';
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
TRUNCATE information_schema.collations;
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
CREATE INDEX my_idx ON information_schema.collations(character_set_name);
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
ALTER TABLE information_schema.collations DROP PRIMARY KEY;
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
ALTER TABLE information_schema.collations ADD f1 INT;
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
ALTER TABLE information_schema.collations ENABLE KEYS;
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
DROP TABLE information_schema.collations;
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
ALTER TABLE information_schema.collations RENAME db_datadict.collations;
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
ALTER TABLE information_schema.collations
|
|
RENAME information_schema.xcollations;
|
|
ERROR 42000: Access denied for user 'root'@'localhost' to database 'information_schema'
|
|
DROP DATABASE db_datadict;
|