Bug #55885 please remove client program versions

• Submitted: 10 Aug 2010 14:57
• Modified: 20 Jan 2017 3:21
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Closed
• Category: MySQL Server: Command-line Clients
• Severity: S4 (Feature request)
• Version: 5.5
• OS: Any
• CPU Architecture: Any

[10 Aug 2010 14:57] Shane Bester

Description:
e.g. in 5.5.5 we have this:

mysqldump  Ver 10.13 Distrib 5.5.5-m3, for Win32 (x86)
mysql  Ver 14.14 Distrib 5.5.5-m3, for Win32 (x86)
mysqlbinlog Ver 3.3 for Win32 at x86
mysql_upgrade  Ver 1.1 Distrib 5.5.5-m3, for Win32 (x86)
perror Ver 2.11, for Win32 (x86)
resolveip.exe Ver 2.3, for Win32 (x86)
mysqlshow  Ver 9.10 Distrib 5.5.5-m3, for Win32 (x86)
mysqlimport  Ver 3.7 Distrib 5.5.5-m3, for Win32 (x86)
myisampack Ver 1.23 for Win32 on x86
myisamchk  Ver 2.7 for Win32 at x86

e.g. in 5.0.48 we have this:
mysqldump  Ver 10.11 Distrib 5.0.48, for Win32 (ia32)
mysql  Ver 14.12 Distrib 5.0.48, for Win32 (ia32)
mysqlbinlog Ver 3.2 for Win32 at ia32
perror Ver 2.10, for Win32 (ia32)
mysqlshow  Ver 9.5 Distrib 5.0.48, for Win32 (ia32)
mysqlimport  Ver 3.5 Distrib 5.0.48, for Win32 (ia32)
myisampack Ver 1.23 for Win32 on ia32
myisamchk  Ver 2.7 for Win32 at ia32

what is their purpose? the versions aren't updated for each change made
to the file. isn't it good enough to print 5.0.48 or 5.5.5-m3 version in the client utils that they are packaged with?

How to repeat:
mysql --help |grep -i distrib
etc

[20 Jan 2017 3:21] Paul DuBois

Posted by developer:
 
Noted in 8.0.1 changelog.

MySQL client and utility programs reported their own program-specific
version number when invoked with the --version option, and the
version strings did not follow a consistent format. Now these
programs print the MySQL version number (same as mysqld) in a
consistent format.