Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2.26, 10.1.41, 10.3.17, 10.4.7
-
None
Description
Most client tools print the associated MariaDB version when the --version option is provided to the tool. For example:
[ec2-user@ip-172-30-0-58 ~]$ mysql --version
|
mysql Ver 15.1 Distrib 10.2.26-MariaDB, for Linux (x86_64) using readline 5.1
|
[ec2-user@ip-172-30-0-58 ~]$ mysqladmin --version
|
mysqladmin Ver 9.1 Distrib 10.2.26-MariaDB, for Linux on x86_64
|
[ec2-user@ip-172-30-0-58 ~]$ mysqldump --version
|
mysqldump Ver 10.16 Distrib 10.2.26-MariaDB, for Linux (x86_64)
|
However, mysqlbinlog doesn't currently do that:
[ec2-user@ip-172-30-0-58 ~]$ mysqlbinlog --version
|
mysqlbinlog Ver 3.3 for Linux at x86_64
|
If we compare the relevant code for mysqlbinlog to the code for mysql, then we can see why:
https://github.com/MariaDB/server/blob/mariadb-10.4.7/client/mysqlbinlog.cc#L1885
https://github.com/MariaDB/server/blob/mariadb-10.4.7/client/mysql.cc#L1711
I think mysqlbinlog should print a more complete version string, like the other client tools.