Bug #82758 | --dba option exclusion error is incomplete | ||
---|---|---|---|
Submitted: | 28 Aug 2016 12:23 | Modified: | 27 Feb 2017 11:24 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Document Store: MySQL Shell | Severity: | S3 (Non-critical) |
Version: | 1.0.4 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[28 Aug 2016 12:23]
Daniël van Eeden
[28 Aug 2016 18:17]
MySQL Verification Team
Hello Daniël, Thank you for the report. Thanks, Umesh
[15 Feb 2017 21:53]
Omar Mendez Andrade
Posted by developer: the dba parameter error message was updated to let hte user know the only available mode for this one is js [root@localhost ~]$ mysqlsh --dba enableXProtocol --uri=root:msandbox@localhost:5717 --sql mysqlx: [Warning] Using a password on the command line interface can be insecure. Creating a Session to 'root@localhost:5717' Classic Session successfully established. No default schema selected. The --dba option can only be used in JavaScript mode [root@localhost ~]$ mysqlsh --dba enableXProtocol --uri=root:msandbox@localhost:5717 --sqlc mysqlx: [Warning] Using a password on the command line interface can be insecure. Creating a Classic Session to 'root@localhost:5717' Session successfully established. No default schema selected. The --dba option can only be used in JavaScript mode [root@localhost ~]$ mysqlsh --dba enableXProtocol --uri=root:msandbox@localhost:5717 --py mysqlx: [Warning] Using a password on the command line interface can be insecure. Creating a Session to 'root@localhost:5717' Classic Session successfully established. No default schema selected. The --dba option can only be used in JavaScript mode [gdlommen@localhost ~]$ mysqlsh --dba enableXProtocol --uri=root:msandbox@localhost:5717 --js mysqlx: [Warning] Using a password on the command line interface can be insecure. Creating a Session to 'root@localhost:5717' Classic Session successfully established. No default schema selected. enableXProtocol: X Protocol plugin is already enabled and listening for connections on port 33060
[27 Feb 2017 11:24]
David Moss
Posted by developer: This change in behavior is clear from the help message. No need to document or add to change log.