MySQL Bugs: #27835: Strange version number encoding for plugins

Bug #27835	Strange version number encoding for plugins
Submitted:	15 Apr 2007 10:14	Modified:	18 Apr 2007 16:22
Reporter:	Hartmut Holzgraefe	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: General	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Plugins only allow two part version numbers for the plugins themselves,
and version information needs to be encoded as hex as 0xMMmm with
MM being the major and mm the minor version.

  (see http://dev.mysql.com/doc/refman/5.1/en/plugin-api-general.html)

The server itself uses a decimal encoded 3 part scheme though:

  mysql-5.1/include/mysql_version.h:#define MYSQL_VERSION_ID 50118

so here we have an encoding of MMmmpp with MM, mm and pp being the
major, minor and patchlevel version info.

IMHO a 3 part version number scheme is way more in sync with the rest
of the world and hex encoding only adds yet another WTF level to it.

Plus having different version encoding schemes in the server itself
and in its plugin infrastructure does not make any sense to me at all.

How to repeat:
See http://dev.mysql.com/doc/refman/5.1/en/plugin-api-general.html,
check for the specification of the "version" field

Thank you for a reasonable feature request. As we have inconsistency with server here, I may even call it a bug.