mariadb/tests
Vladislav Vaintroub 2f075a1e37 Bug #47423 mtr connects to wrong database
The reason for the bug is that mysqtest as well as other client tools
running in test suite (mysqlbinlog, mysqldump) will first try to connect 
whatever database has created shared memory with default base name 
"MySQL" and use this. (Same effect could be seen on Unix if mtr would
not care to calculate "port" and "socket" parameter).
      
The fix ensures that all client tools and  running in mtr use unique  
per-database shared memory base parameters, so there is no possibility
to clash with already installed one. We use socket name for shared memory 
base (it's known to be unique). This shared-memory-base is written to the
MTR config file to the [client] and [mysqld] sections. Fix made also made 
sure all client tools understand and correctly handle --shared-memory-base.
Prior to this patch  it was not the case for  mysqltest, mysqlbinlog and 
mysql_client_test.
      
All new connections done from mtr scripts via connect() will by default 
set shared-memory-base. And finally, there is a possibility to force 
shared memory or pipe connection and overwrite shared memory/pipe base name
from within mtr scripts via optional PIPE or SHM modifier. This functionality
was manually backported from 6.0
(original patch  http://lists.mysql.com/commits/74749)
2009-11-03 01:19:37 +01:00
..
.cvsignore
auto_increment.res
auto_increment.tst
big_record.pl
bug25714.c
CMakeLists.txt
connect_test.c
deadlock_test.c
drop_test.pl
export.pl
fork2_test.pl
fork_big.pl
fork_big2.pl
function.res
function.tst
grant.pl
grant.res
index_corrupt.pl
insert_and_repair.pl
insert_test.c
list_test.c
lock_test.pl
lock_test.res
mail_to_db.pl
Makefile.am
myisam-big-rows.tst
mysql_client_test.c Bug #47423 mtr connects to wrong database 2009-11-03 01:19:37 +01:00
pmail.pl
rename_test.pl
restore-lock.smack
select_test.c
showdb_test.c
ssl_test.c
table_types.pl
test_delayed_insert.pl
thread_test.c
truncate.pl