mariadb/mysql-test/t/named_pipe.test

# We currently only have named pipe support on windows, so
# in order  to optimize things we skip this test on all
# other platforms
--source include/windows.inc

# Only run this test if named pipe is avaliable
let $nmp= query_get_value("SHOW VARIABLES LIKE 'named_pipe'", Value, 1);
if (`SELECT '$nmp' != 'ON'`){
  skip No named pipe support;
}

# Connect using named pipe for testing
connect(pipe_con,localhost,root,,,,,PIPE);

# Source select test case
-- source include/common-tests.inc

connection default;
disconnect pipe_con;
Add test for named pipes on windows Improve test for shm on windows 2007-09-24 12:42:44 +02:00			`# We currently only have named pipe support on windows, so`
			`# in order to optimize things we skip this test on all`
			`# other platforms`
			`--source include/windows.inc`

			`# Only run this test if named pipe is avaliable`
			`let $nmp= query_get_value("SHOW VARIABLES LIKE 'named_pipe'", Value, 1);`
			if (`SELECT '$nmp' != 'ON'`){
			`skip No named pipe support;`
			`}`

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			`# Connect using named pipe for testing`
			`connect(pipe_con,localhost,root,,,,,PIPE);`

Add test for named pipes on windows Improve test for shm on windows 2007-09-24 12:42:44 +02:00			`# Source select test case`
			`-- source include/common-tests.inc`

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			`connection default;`
			`disconnect pipe_con;`