Bug #99283 mysql --binary-as-hex default is confusing

Submitted: 16 Apr 2020 19:23 Modified: 16 Apr 2020 22:05
Reporter: Morgan Tocker Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:8.0.19+ OS:Any
Assigned to: CPU Architecture:Any

[16 Apr 2020 19:23] Morgan Tocker
Description:
In MySQL 8.0.19 the default for --binary-as-hex changed to ON for interactive sessions. See: https://dev.mysql.com/worklog/task/?id=13038

The problem is, this is non-obvious to users because to a naive user it looks like the default is "OFF":

$ mysql --help | grep binary-as-hex
  --binary-as-hex     Print binary data as hex
binary-as-hex                     FALSE

Which leads to confusion, is it a different setting that is responsible? Nope, the default printed here is for non-interactive.

How to repeat:
See description

Suggested fix:
Is it possible to list the default as something like AUTO? That makes it clear it's contextual.

.. and thanks for changing the default by the way. Much better!
[16 Apr 2020 22:05] MySQL Verification Team
Thank you for the bug report.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.038 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.