mariadb/mysql-test/main/grant_read_only.test
Dmitry Shulga eeb00ceffd MDEV-35617: DROP USER should leave no active session for that user
Follow-up patch with adjustments of test files and updates of result
files for tests.

Some of tests were rewritten slighlty. Everywhere where common
pattern used:
-----
  CREATE USER userA;
  --connect con1 ... userA ...
   <sql statements...>
  --disconnect con1
  DROP USER userA;
-----
the DROP USER statement has been eclosed into the directive
--disable_warnings
--enable_warnings

This change is caused by the race conddition between --disconnect
and DROP USER since a number of currently running sessions
established on behalf the user being dropped is counted by
holding the rw_lock THD_list_iterator::lock that is not acquired on
execution the DROP USER statement but the lock is taken as the last
step on handling disconnection (when the client is already sending
the next statement). Therefore, for the cases where the command
 --disconnect precedes the DROP USER statement
we hide the possible warnings about presence of active sessions
for the user being deleted to make tests deterministic.
2025-06-09 18:24:28 +07:00

95 lines
2.3 KiB
Text

-- source include/not_embedded.inc
--echo #
--echo # Start of 10.5 tests
--echo #
--echo #
--echo # Test that @@read_only is not ignored without READ_ONLY ADMIN or SUPER
--echo #
CREATE TABLE t1 (a INT);
CREATE USER user1@localhost IDENTIFIED BY '';
GRANT ALL PRIVILEGES ON *.* TO user1@localhost;
REVOKE READ_ONLY ADMIN, SUPER ON *.* FROM user1@localhost;
SET @@GLOBAL.read_only=1;
connect (con1,localhost,user1,,);
connection con1;
--error ER_OPTION_PREVENTS_STATEMENT
UPDATE t1 SET a=11 WHERE a=10;
--error ER_OPTION_PREVENTS_STATEMENT
DELETE FROM t1 WHERE a=11;
--error ER_OPTION_PREVENTS_STATEMENT
INSERT INTO t1 VALUES (20);
disconnect con1;
connection default;
SET @@GLOBAL.read_only=0;
--disable_warnings
DROP USER user1@localhost;
--enable_warnings
DROP TABLE t1;
--echo #
--echo # Test that @@read_only is ignored with READ_ONLY ADMIN
--echo #
CREATE TABLE t1 (a INT);
CREATE USER user1@localhost IDENTIFIED BY '';
## TODO: it works even without INSERT/UPDATE/DELETE: file a bug report!
GRANT SELECT, INSERT, UPDATE, DELETE, READ_ONLY ADMIN ON *.* TO user1@localhost;
SHOW GRANTS FOR user1@localhost;
SET @@GLOBAL.read_only=1;
connect (con1,localhost,user1,,);
connection con1;
SELECT @@read_only;
UPDATE t1 SET a=11 WHERE a=10;
DELETE FROM t1 WHERE a=11;
INSERT INTO t1 VALUES (20);
disconnect con1;
connection default;
SET @@GLOBAL.read_only=0;
--disable_warnings
DROP USER user1@localhost;
--enable_warnings
DROP TABLE t1;
--echo #
--echo # Test that @@read_only is not ignored with SUPER
--echo #
CREATE TABLE t1 (a INT);
CREATE USER user1@localhost IDENTIFIED BY '';
## TODO: it works even without INSERT/UPDATE/DELETE: file a bug report!
GRANT SELECT, INSERT, UPDATE, DELETE, SUPER ON *.* TO user1@localhost;
SHOW GRANTS FOR user1@localhost;
SET @@GLOBAL.read_only=1;
connect (con1,localhost,user1,,);
connection con1;
SELECT @@read_only;
--error ER_OPTION_PREVENTS_STATEMENT
UPDATE t1 SET a=11 WHERE a=10;
--error ER_OPTION_PREVENTS_STATEMENT
DELETE FROM t1 WHERE a=11;
connection default;
grant read only admin on *.* to user1@localhost;
disconnect con1;
connect (con1,localhost,user1,,);
INSERT INTO t1 VALUES (20);
disconnect con1;
connection default;
SET @@GLOBAL.read_only=0;
--disable_warnings
DROP USER user1@localhost;
--enable_warnings
DROP TABLE t1;
--echo #
--echo # End of 10.5 tests
--echo #