diff options
| author | Brandon Nesterenko <brandon.nesterenko@mariadb.com> | 2021-05-10 11:10:53 -0600 |
|---|---|---|
| committer | Brandon Nesterenko <brandon.nesterenko@mariadb.com> | 2021-05-11 11:50:41 -0600 |
| commit | b6cfb2961ec72f827468d6d2f7583ce7d1127f6e (patch) | |
| tree | 555764832f93e7082666c884e8219238d1deed5d /mysql-test/main/cli_options_force_protocol_win.result | |
| parent | 02380cd3845e699600b3f7e05da30f0fed3ddd20 (diff) | |
| download | mariadb-git-b6cfb2961ec72f827468d6d2f7583ce7d1127f6e.tar.gz | |
MDEV-14974: --port ignored for --host=localhost
Problem:
=======
MariaDB's command line utilities (e.g., mysql,
mysqldump, etc) silently ignore connection
property options (e.g., --port and --socket)
when protocol is not explicitly set via the
command-line for localhost connections.
Fix:
===
If connection properties are specified without a
protocol, override the protocol to be consistent.
For example, if --port is specified, automatically
set protocol=tcp.
Caveats:
=======
* When multiple connection properties are
specified, nothing is overridden
* If protocol is is set via the command-line,
its value is used
Reviewers:
========
Sergei Golubchik <serg@mariadb.com>
Vladislav Vaintroub <wlad@mariadb.com>
Diffstat (limited to 'mysql-test/main/cli_options_force_protocol_win.result')
| -rw-r--r-- | mysql-test/main/cli_options_force_protocol_win.result | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/mysql-test/main/cli_options_force_protocol_win.result b/mysql-test/main/cli_options_force_protocol_win.result new file mode 100644 index 00000000000..4fffc2a4837 --- /dev/null +++ b/mysql-test/main/cli_options_force_protocol_win.result @@ -0,0 +1,24 @@ +# +# MDEV-14974: --port ignored for --host=localhost +# +# +# The following group of tests should produce no warnings +# +# exec MYSQL --host=localhost -e "status" 2>&1 | findstr /c:"Connection:" /c:"WARNING:" +Connection: localhost via TCP/IP +# exec MYSQL --host=localhost --port=MASTER_MYPORT -e "status" 2>&1 | findstr /c:"Connection:" /c:"WARNING:" +Connection: localhost via TCP/IP +# exec MYSQL --host=localhost --port=MASTER_MYPORT --socket=MASTER_MYSOCK -e "status" 2>&1 | findstr /c:"Connection:" /c:"WARNING:" +Connection: localhost via TCP/IP +# exec MYSQL --host=localhost --protocol=pipe -e "status" 2>&1 | findstr /c:"Connection:" /c:"WARNING:" +Connection: localhost via named pipe +# exec MYSQL --host=localhost -W -e "status" 2>&1 | findstr /c:"Connection:" /c:"WARNING:" +Connection: localhost via named pipe +# exec MYSQL --host=localhost -W --socket=MASTER_MYSOCK -e "status" 2>&1 | findstr /c:"Connection:" /c:"WARNING:" +Connection: localhost via named pipe +# +# The remaining tests should produce warnings +# +# exec MYSQL --host=localhost --socket=MASTER_MYSOCK -e "status" 2>&1 | findstr /c:"Connection:" /c:"WARNING:" +WARNING: Forcing protocol to PIPE due to option specification. Please explicitly state intended protocol. +Connection: localhost via named pipe |
