2005-09-08 10:09:30 +02:00
|
|
|
drop table if exists t1,t2;
|
2002-12-05 12:01:15 +01:00
|
|
|
show tables;
|
2004-10-10 12:15:14 +02:00
|
|
|
Tables_in_mysql
|
|
|
|
|
columns_priv
|
|
|
|
|
db
|
2006-01-10 19:16:58 +01:00
|
|
|
event
|
2004-10-10 12:15:14 +02:00
|
|
|
func
|
2006-01-19 03:56:06 +01:00
|
|
|
general_log
|
2004-10-10 12:15:14 +02:00
|
|
|
help_category
|
|
|
|
|
help_keyword
|
|
|
|
|
help_relation
|
|
|
|
|
help_topic
|
|
|
|
|
host
|
2006-12-01 15:49:07 +01:00
|
|
|
ndb_binlog_index
|
2005-11-06 13:13:06 +01:00
|
|
|
plugin
|
2004-10-10 12:15:14 +02:00
|
|
|
proc
|
2004-12-23 11:46:24 +01:00
|
|
|
procs_priv
|
2010-11-02 16:45:26 +01:00
|
|
|
proxies_priv
|
2006-12-09 04:19:51 +01:00
|
|
|
servers
|
2006-01-19 03:56:06 +01:00
|
|
|
slow_log
|
2004-10-10 12:15:14 +02:00
|
|
|
tables_priv
|
|
|
|
|
time_zone
|
|
|
|
|
time_zone_leap_second
|
|
|
|
|
time_zone_name
|
|
|
|
|
time_zone_transition
|
|
|
|
|
time_zone_transition_type
|
|
|
|
|
user
|
2002-12-05 12:01:15 +01:00
|
|
|
show tables;
|
2004-10-10 12:15:14 +02:00
|
|
|
Tables_in_test
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,root,z,test2,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'root'@'localhost' (using password: YES)
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,root,z,test,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'root'@'localhost' (using password: YES)
|
2002-12-05 12:01:15 +01:00
|
|
|
grant ALL on *.* to test@localhost identified by "gambling";
|
|
|
|
|
grant ALL on *.* to test@127.0.0.1 identified by "gambling";
|
|
|
|
|
show tables;
|
2004-10-10 12:15:14 +02:00
|
|
|
Tables_in_mysql
|
|
|
|
|
columns_priv
|
|
|
|
|
db
|
2006-01-10 19:16:58 +01:00
|
|
|
event
|
2004-10-10 12:15:14 +02:00
|
|
|
func
|
2006-01-19 03:56:06 +01:00
|
|
|
general_log
|
2004-10-10 12:15:14 +02:00
|
|
|
help_category
|
|
|
|
|
help_keyword
|
|
|
|
|
help_relation
|
|
|
|
|
help_topic
|
|
|
|
|
host
|
2006-12-01 15:49:07 +01:00
|
|
|
ndb_binlog_index
|
2005-11-06 13:13:06 +01:00
|
|
|
plugin
|
2004-10-10 12:15:14 +02:00
|
|
|
proc
|
2004-12-23 11:46:24 +01:00
|
|
|
procs_priv
|
2010-11-02 16:45:26 +01:00
|
|
|
proxies_priv
|
2006-12-09 04:19:51 +01:00
|
|
|
servers
|
2006-01-19 03:56:06 +01:00
|
|
|
slow_log
|
2004-10-10 12:15:14 +02:00
|
|
|
tables_priv
|
|
|
|
|
time_zone
|
|
|
|
|
time_zone_leap_second
|
|
|
|
|
time_zone_name
|
|
|
|
|
time_zone_transition
|
|
|
|
|
time_zone_transition_type
|
|
|
|
|
user
|
2002-12-05 12:01:15 +01:00
|
|
|
show tables;
|
2004-10-10 12:15:14 +02:00
|
|
|
Tables_in_test
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,test,,test2,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'test'@'localhost' (using password: NO)
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,test,,"",MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'test'@'localhost' (using password: NO)
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,test,zorro,test2,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'test'@'localhost' (using password: YES)
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,test,zorro,test,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'test'@'localhost' (using password: YES)
|
2004-07-08 15:54:07 +02:00
|
|
|
update mysql.user set password=old_password("gambling2") where user=_binary"test";
|
2002-12-05 12:01:15 +01:00
|
|
|
flush privileges;
|
2004-08-26 17:26:38 +02:00
|
|
|
set password="";
|
2004-07-30 22:05:08 +02:00
|
|
|
set password='gambling3';
|
|
|
|
|
ERROR HY000: Password hash should be a 41-digit hexadecimal number
|
2003-07-08 00:36:14 +02:00
|
|
|
set password=old_password('gambling3');
|
2002-12-05 12:01:15 +01:00
|
|
|
show tables;
|
2004-10-10 12:15:14 +02:00
|
|
|
Tables_in_mysql
|
|
|
|
|
columns_priv
|
|
|
|
|
db
|
2006-01-10 19:16:58 +01:00
|
|
|
event
|
2004-10-10 12:15:14 +02:00
|
|
|
func
|
2006-01-19 03:56:06 +01:00
|
|
|
general_log
|
2004-10-10 12:15:14 +02:00
|
|
|
help_category
|
|
|
|
|
help_keyword
|
|
|
|
|
help_relation
|
|
|
|
|
help_topic
|
|
|
|
|
host
|
2006-12-01 15:49:07 +01:00
|
|
|
ndb_binlog_index
|
2005-11-06 13:13:06 +01:00
|
|
|
plugin
|
2004-10-10 12:15:14 +02:00
|
|
|
proc
|
2004-12-23 11:46:24 +01:00
|
|
|
procs_priv
|
2010-11-02 16:45:26 +01:00
|
|
|
proxies_priv
|
2006-12-09 04:19:51 +01:00
|
|
|
servers
|
2006-01-19 03:56:06 +01:00
|
|
|
slow_log
|
2004-10-10 12:15:14 +02:00
|
|
|
tables_priv
|
|
|
|
|
time_zone
|
|
|
|
|
time_zone_leap_second
|
|
|
|
|
time_zone_name
|
|
|
|
|
time_zone_transition
|
|
|
|
|
time_zone_transition_type
|
|
|
|
|
user
|
2002-12-05 12:01:15 +01:00
|
|
|
show tables;
|
2004-10-10 12:15:14 +02:00
|
|
|
Tables_in_test
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,test,,test2,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'test'@'localhost' (using password: NO)
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,test,,test,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'test'@'localhost' (using password: NO)
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,test,zorro,test2,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'test'@'localhost' (using password: YES)
|
2005-11-07 22:30:44 +01:00
|
|
|
connect(localhost,test,zorro,test,MASTER_PORT,MASTER_SOCKET);
|
2005-10-12 13:56:07 +02:00
|
|
|
ERROR 28000: Access denied for user 'test'@'localhost' (using password: YES)
|
2004-07-08 15:54:07 +02:00
|
|
|
delete from mysql.user where user=_binary"test";
|
2003-06-13 11:17:31 +02:00
|
|
|
flush privileges;
|
2005-08-30 15:22:19 +02:00
|
|
|
create table t1 (id integer not null auto_increment primary key);
|
|
|
|
|
create temporary table t2(id integer not null auto_increment primary key);
|
|
|
|
|
set @id := 1;
|
|
|
|
|
delete from t1 where id like @id;
|
2005-09-08 10:09:30 +02:00
|
|
|
drop table t1;
|
2008-03-12 15:44:40 +01:00
|
|
|
# ------------------------------------------------------------------
|
|
|
|
|
# -- End of 4.1 tests
|
|
|
|
|
# ------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
# -- Bug#33507: Event scheduler creates more threads than max_connections
|
|
|
|
|
# -- which results in user lockout.
|
|
|
|
|
|
|
|
|
|
GRANT USAGE ON *.* TO mysqltest_u1@localhost;
|
|
|
|
|
|
|
|
|
|
SET GLOBAL max_connections = 3;
|
|
|
|
|
SET GLOBAL event_scheduler = ON;
|
|
|
|
|
|
Avoid races in connect.test.
The problem was in a test case for Bug33507:
- when the number of active connections reaches the limit,
the server accepts only root connections. That's achieved by
accepting a connection, negotiating with the client and
checking user credentials. If it is not SUPER, the connection
is dropped.
- when the server accepts connection, it increases the counter;
- when the server drops connection, it decreases the counter;
- the race was in between of decreasing the counter and accepting
new connection:
- max_user_connections = 2;
- 2 oridinary user connections accepted;
- extra user connection is establishing;
- server checked user credentials, and sent 'Too many connections'
error;
- the client receives the error and establishes extra SUPER user
connection;
- the server however didn't decrease the counter (the extra
user connection still is "alive" in the server) -- so, the new
SUPER-user connection, will be dropped, because it exceeds
(max_user_connections + 1).
The fix is to implement "safe connect", which makes several attempts
to connect and use it in the test script.
mysql-test/r/connect.result:
Update test file.
mysql-test/t/connect.test:
Avoid races in connect.test.
mysql-test/include/connect2.inc:
Auxiliary routine to establish a connection reliably.
2008-03-17 12:26:00 +01:00
|
|
|
# -- Waiting for Event Scheduler to start...
|
2008-03-12 15:44:40 +01:00
|
|
|
|
|
|
|
|
# -- Disconnecting default connection...
|
|
|
|
|
|
|
|
|
|
# -- Check that we allow exactly three user connections, no matter how
|
|
|
|
|
# -- many threads are running.
|
|
|
|
|
|
|
|
|
|
# -- Connecting (1)...
|
Avoid races in connect.test.
The problem was in a test case for Bug33507:
- when the number of active connections reaches the limit,
the server accepts only root connections. That's achieved by
accepting a connection, negotiating with the client and
checking user credentials. If it is not SUPER, the connection
is dropped.
- when the server accepts connection, it increases the counter;
- when the server drops connection, it decreases the counter;
- the race was in between of decreasing the counter and accepting
new connection:
- max_user_connections = 2;
- 2 oridinary user connections accepted;
- extra user connection is establishing;
- server checked user credentials, and sent 'Too many connections'
error;
- the client receives the error and establishes extra SUPER user
connection;
- the server however didn't decrease the counter (the extra
user connection still is "alive" in the server) -- so, the new
SUPER-user connection, will be dropped, because it exceeds
(max_user_connections + 1).
The fix is to implement "safe connect", which makes several attempts
to connect and use it in the test script.
mysql-test/r/connect.result:
Update test file.
mysql-test/t/connect.test:
Avoid races in connect.test.
mysql-test/include/connect2.inc:
Auxiliary routine to establish a connection reliably.
2008-03-17 12:26:00 +01:00
|
|
|
# -- Establishing connection 'con_1' (user: mysqltest_u1)...
|
|
|
|
|
# -- Connection 'con_1' has been established.
|
2008-03-12 15:44:40 +01:00
|
|
|
|
|
|
|
|
# -- Connecting (2)...
|
Avoid races in connect.test.
The problem was in a test case for Bug33507:
- when the number of active connections reaches the limit,
the server accepts only root connections. That's achieved by
accepting a connection, negotiating with the client and
checking user credentials. If it is not SUPER, the connection
is dropped.
- when the server accepts connection, it increases the counter;
- when the server drops connection, it decreases the counter;
- the race was in between of decreasing the counter and accepting
new connection:
- max_user_connections = 2;
- 2 oridinary user connections accepted;
- extra user connection is establishing;
- server checked user credentials, and sent 'Too many connections'
error;
- the client receives the error and establishes extra SUPER user
connection;
- the server however didn't decrease the counter (the extra
user connection still is "alive" in the server) -- so, the new
SUPER-user connection, will be dropped, because it exceeds
(max_user_connections + 1).
The fix is to implement "safe connect", which makes several attempts
to connect and use it in the test script.
mysql-test/r/connect.result:
Update test file.
mysql-test/t/connect.test:
Avoid races in connect.test.
mysql-test/include/connect2.inc:
Auxiliary routine to establish a connection reliably.
2008-03-17 12:26:00 +01:00
|
|
|
# -- Establishing connection 'con_2' (user: mysqltest_u1)...
|
|
|
|
|
# -- Connection 'con_2' has been established.
|
|
|
|
|
|
2008-03-12 15:44:40 +01:00
|
|
|
# -- Connecting (3)...
|
Avoid races in connect.test.
The problem was in a test case for Bug33507:
- when the number of active connections reaches the limit,
the server accepts only root connections. That's achieved by
accepting a connection, negotiating with the client and
checking user credentials. If it is not SUPER, the connection
is dropped.
- when the server accepts connection, it increases the counter;
- when the server drops connection, it decreases the counter;
- the race was in between of decreasing the counter and accepting
new connection:
- max_user_connections = 2;
- 2 oridinary user connections accepted;
- extra user connection is establishing;
- server checked user credentials, and sent 'Too many connections'
error;
- the client receives the error and establishes extra SUPER user
connection;
- the server however didn't decrease the counter (the extra
user connection still is "alive" in the server) -- so, the new
SUPER-user connection, will be dropped, because it exceeds
(max_user_connections + 1).
The fix is to implement "safe connect", which makes several attempts
to connect and use it in the test script.
mysql-test/r/connect.result:
Update test file.
mysql-test/t/connect.test:
Avoid races in connect.test.
mysql-test/include/connect2.inc:
Auxiliary routine to establish a connection reliably.
2008-03-17 12:26:00 +01:00
|
|
|
# -- Establishing connection 'con_3' (user: mysqltest_u1)...
|
|
|
|
|
# -- Connection 'con_3' has been established.
|
2008-03-12 15:44:40 +01:00
|
|
|
|
Avoid races in connect.test.
The problem was in a test case for Bug33507:
- when the number of active connections reaches the limit,
the server accepts only root connections. That's achieved by
accepting a connection, negotiating with the client and
checking user credentials. If it is not SUPER, the connection
is dropped.
- when the server accepts connection, it increases the counter;
- when the server drops connection, it decreases the counter;
- the race was in between of decreasing the counter and accepting
new connection:
- max_user_connections = 2;
- 2 oridinary user connections accepted;
- extra user connection is establishing;
- server checked user credentials, and sent 'Too many connections'
error;
- the client receives the error and establishes extra SUPER user
connection;
- the server however didn't decrease the counter (the extra
user connection still is "alive" in the server) -- so, the new
SUPER-user connection, will be dropped, because it exceeds
(max_user_connections + 1).
The fix is to implement "safe connect", which makes several attempts
to connect and use it in the test script.
mysql-test/r/connect.result:
Update test file.
mysql-test/t/connect.test:
Avoid races in connect.test.
mysql-test/include/connect2.inc:
Auxiliary routine to establish a connection reliably.
2008-03-17 12:26:00 +01:00
|
|
|
# -- Connecting (4) [should fail]...
|
|
|
|
|
# -- Establishing connection 'con_4' (user: mysqltest_u1)...
|
|
|
|
|
# -- Error: can not establish connection 'con_4'.
|
2008-03-12 15:44:40 +01:00
|
|
|
|
|
|
|
|
# -- Check that we allow one extra SUPER-user connection.
|
|
|
|
|
|
|
|
|
|
# -- Connecting super (1)...
|
Avoid races in connect.test.
The problem was in a test case for Bug33507:
- when the number of active connections reaches the limit,
the server accepts only root connections. That's achieved by
accepting a connection, negotiating with the client and
checking user credentials. If it is not SUPER, the connection
is dropped.
- when the server accepts connection, it increases the counter;
- when the server drops connection, it decreases the counter;
- the race was in between of decreasing the counter and accepting
new connection:
- max_user_connections = 2;
- 2 oridinary user connections accepted;
- extra user connection is establishing;
- server checked user credentials, and sent 'Too many connections'
error;
- the client receives the error and establishes extra SUPER user
connection;
- the server however didn't decrease the counter (the extra
user connection still is "alive" in the server) -- so, the new
SUPER-user connection, will be dropped, because it exceeds
(max_user_connections + 1).
The fix is to implement "safe connect", which makes several attempts
to connect and use it in the test script.
mysql-test/r/connect.result:
Update test file.
mysql-test/t/connect.test:
Avoid races in connect.test.
mysql-test/include/connect2.inc:
Auxiliary routine to establish a connection reliably.
2008-03-17 12:26:00 +01:00
|
|
|
# -- Establishing connection 'con_super_1' (user: root)...
|
|
|
|
|
# -- Connection 'con_super_1' has been established.
|
|
|
|
|
|
|
|
|
|
# -- Connecting super (2) [should fail]...
|
|
|
|
|
# -- Establishing connection 'con_super_2' (user: root)...
|
|
|
|
|
# -- Error: can not establish connection 'con_super_2'.
|
2008-03-12 15:44:40 +01:00
|
|
|
|
Avoid races in connect.test.
The problem was in a test case for Bug33507:
- when the number of active connections reaches the limit,
the server accepts only root connections. That's achieved by
accepting a connection, negotiating with the client and
checking user credentials. If it is not SUPER, the connection
is dropped.
- when the server accepts connection, it increases the counter;
- when the server drops connection, it decreases the counter;
- the race was in between of decreasing the counter and accepting
new connection:
- max_user_connections = 2;
- 2 oridinary user connections accepted;
- extra user connection is establishing;
- server checked user credentials, and sent 'Too many connections'
error;
- the client receives the error and establishes extra SUPER user
connection;
- the server however didn't decrease the counter (the extra
user connection still is "alive" in the server) -- so, the new
SUPER-user connection, will be dropped, because it exceeds
(max_user_connections + 1).
The fix is to implement "safe connect", which makes several attempts
to connect and use it in the test script.
mysql-test/r/connect.result:
Update test file.
mysql-test/t/connect.test:
Avoid races in connect.test.
mysql-test/include/connect2.inc:
Auxiliary routine to establish a connection reliably.
2008-03-17 12:26:00 +01:00
|
|
|
# -- Ensure that we have Event Scheduler thread, 3 ordinary user
|
|
|
|
|
# -- connections and one extra super-user connection.
|
2008-03-12 15:44:40 +01:00
|
|
|
SELECT user FROM information_schema.processlist ORDER BY id;
|
|
|
|
|
user
|
|
|
|
|
event_scheduler
|
|
|
|
|
mysqltest_u1
|
|
|
|
|
mysqltest_u1
|
|
|
|
|
mysqltest_u1
|
|
|
|
|
root
|
|
|
|
|
|
|
|
|
|
# -- Resetting variables...
|
|
|
|
|
SET GLOBAL max_connections = 151;
|
2008-03-13 10:02:12 +01:00
|
|
|
|
|
|
|
|
# -- Stopping Event Scheduler...
|
2008-03-12 15:44:40 +01:00
|
|
|
SET GLOBAL event_scheduler = OFF;
|
Avoid races in connect.test.
The problem was in a test case for Bug33507:
- when the number of active connections reaches the limit,
the server accepts only root connections. That's achieved by
accepting a connection, negotiating with the client and
checking user credentials. If it is not SUPER, the connection
is dropped.
- when the server accepts connection, it increases the counter;
- when the server drops connection, it decreases the counter;
- the race was in between of decreasing the counter and accepting
new connection:
- max_user_connections = 2;
- 2 oridinary user connections accepted;
- extra user connection is establishing;
- server checked user credentials, and sent 'Too many connections'
error;
- the client receives the error and establishes extra SUPER user
connection;
- the server however didn't decrease the counter (the extra
user connection still is "alive" in the server) -- so, the new
SUPER-user connection, will be dropped, because it exceeds
(max_user_connections + 1).
The fix is to implement "safe connect", which makes several attempts
to connect and use it in the test script.
mysql-test/r/connect.result:
Update test file.
mysql-test/t/connect.test:
Avoid races in connect.test.
mysql-test/include/connect2.inc:
Auxiliary routine to establish a connection reliably.
2008-03-17 12:26:00 +01:00
|
|
|
|
2008-03-13 10:02:12 +01:00
|
|
|
# -- Waiting for Event Scheduler to stop...
|
2008-03-12 15:44:40 +01:00
|
|
|
|
|
|
|
|
# -- That's it. Closing connections...
|
|
|
|
|
|
|
|
|
|
# -- Restoring default connection...
|
|
|
|
|
|
2008-03-13 10:02:12 +01:00
|
|
|
# -- Waiting for connections to close...
|
|
|
|
|
|
|
|
|
|
DROP USER mysqltest_u1@localhost;
|
|
|
|
|
|
2008-03-12 15:44:40 +01:00
|
|
|
# -- End of Bug#33507.
|
|
|
|
|
|
2009-03-06 15:56:17 +01:00
|
|
|
# -- Bug#35074: max_used_connections is not correct.
|
2008-03-13 10:02:12 +01:00
|
|
|
|
|
|
|
|
FLUSH STATUS;
|
|
|
|
|
|
|
|
|
|
SHOW STATUS LIKE 'max_used_connections';
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Max_used_connections 1
|
|
|
|
|
|
|
|
|
|
# -- Starting Event Scheduler...
|
|
|
|
|
SET GLOBAL event_scheduler = ON;
|
|
|
|
|
# -- Waiting for Event Scheduler to start...
|
|
|
|
|
|
|
|
|
|
# -- Opening a new connection to check max_used_connections...
|
|
|
|
|
|
|
|
|
|
# -- Check that max_used_connections hasn't changed.
|
|
|
|
|
SHOW STATUS LIKE 'max_used_connections';
|
|
|
|
|
Variable_name Value
|
|
|
|
|
Max_used_connections 2
|
|
|
|
|
|
|
|
|
|
# -- Closing new connection...
|
|
|
|
|
|
|
|
|
|
# -- Stopping Event Scheduler...
|
|
|
|
|
SET GLOBAL event_scheduler = OFF;
|
|
|
|
|
# -- Waiting for Event Scheduler to stop...
|
|
|
|
|
|
|
|
|
|
# -- End of Bug#35074.
|
|
|
|
|
|
2009-03-18 16:46:32 +01:00
|
|
|
SELECT 'Connection on extra port ok';
|
|
|
|
|
Connection on extra port ok
|
|
|
|
|
Connection on extra port ok
|
|
|
|
|
SELECT 'Connection on extra port 2 ok';
|
|
|
|
|
Connection on extra port 2 ok
|
|
|
|
|
Connection on extra port 2 ok
|
|
|
|
|
# -- Success: more than --extra-max-connections + 1 normal connections not possible
|
2010-11-11 08:34:14 +01:00
|
|
|
#
|
|
|
|
|
# -- Bug#49752: 2469.126.2 unintentionally breaks authentication
|
|
|
|
|
# against MySQL 5.1 server
|
|
|
|
|
#
|
|
|
|
|
GRANT ALL ON test.* TO 'Azundris12345678'@'localhost' IDENTIFIED BY 'test123';
|
|
|
|
|
FLUSH PRIVILEGES;
|
|
|
|
|
DROP USER 'Azundris12345678'@'localhost';
|
|
|
|
|
FLUSH PRIVILEGES;
|
|
|
|
|
#
|
|
|
|
|
# -- End of Bug#49752
|
|
|
|
|
#
|
2008-03-12 15:44:40 +01:00
|
|
|
# ------------------------------------------------------------------
|
|
|
|
|
# -- End of 5.1 tests
|
|
|
|
|
# ------------------------------------------------------------------
|
2010-04-05 11:50:31 +02:00
|
|
|
CREATE USER mysqltest_up1 IDENTIFIED VIA mysql_native_password using '*E8D46CE25265E545D225A8A6F1BAF642FEBEE5CB';
|
|
|
|
|
CREATE USER mysqltest_up2 IDENTIFIED VIA mysql_old_password using '09301740536db389';
|
2010-04-06 20:36:06 +02:00
|
|
|
connect(localhost,mysqltest_up1,foo,test,MASTER_PORT,MASTER_SOCKET);
|
2010-04-05 11:50:31 +02:00
|
|
|
ERROR 28000: Access denied for user 'mysqltest_up1'@'localhost' (using password: YES)
|
|
|
|
|
select user(), current_user();
|
|
|
|
|
user() current_user()
|
|
|
|
|
mysqltest_up1@localhost mysqltest_up1@%
|
2010-04-06 20:36:06 +02:00
|
|
|
connect(localhost,mysqltest_up2,newpw,test,MASTER_PORT,MASTER_SOCKET);
|
2010-04-05 11:50:31 +02:00
|
|
|
ERROR 28000: Access denied for user 'mysqltest_up2'@'localhost' (using password: YES)
|
|
|
|
|
select user(), current_user();
|
|
|
|
|
user() current_user()
|
|
|
|
|
mysqltest_up2@localhost mysqltest_up2@%
|
2010-12-20 19:19:24 +01:00
|
|
|
connect(localhost,mysqltest_nouser,newpw,test,MASTER_PORT,MASTER_SOCKET);
|
|
|
|
|
ERROR 28000: Access denied for user 'mysqltest_nouser'@'localhost' (using password: YES)
|
|
|
|
|
connect(localhost,mysqltest_nouser,,test,MASTER_PORT,MASTER_SOCKET);
|
|
|
|
|
ERROR 28000: Access denied for user 'mysqltest_nouser'@'localhost' (using password: NO)
|
2010-04-05 11:50:31 +02:00
|
|
|
DROP USER mysqltest_up1@'%';
|
|
|
|
|
DROP USER mysqltest_up2@'%';
|
2012-06-10 11:50:21 +02:00
|
|
|
#
|
|
|
|
|
# BUG#1010351: New "via" keyword in 5.2+ can't be used as identifier anymore
|
|
|
|
|
#
|
|
|
|
|
create table t1 (via int);
|
|
|
|
|
alter table t1 add key(via);
|
|
|
|
|
drop table t1;
|
|
|
|
|
create table t1 (col1 int);
|
|
|
|
|
alter table t1 add via int not null;
|
|
|
|
|
drop table t1;
|
|
|
|
|
drop procedure if exists p1;
|
|
|
|
|
create procedure p1(x int)
|
|
|
|
|
foo: loop
|
|
|
|
|
if x = 0 then
|
|
|
|
|
leave foo;
|
|
|
|
|
end if;
|
|
|
|
|
select 'test';
|
|
|
|
|
set x = x-1;
|
|
|
|
|
end loop foo|
|
|
|
|
|
call p1(2);
|
|
|
|
|
test
|
|
|
|
|
test
|
|
|
|
|
test
|
|
|
|
|
test
|
|
|
|
|
drop procedure p1;
|