Description:
I'm looking at the official public bazaar source:
psergey@foxhole mysql-server-5.4 $ bzr parent
http://bazaar.launchpad.net/%7Emysql/mysql-server/mysql-5.4/
and I see there the following (irrelevant output lines omitted):
sergey@foxhole mysql-server-5.4 $ grep WARN_DEP sql/*
...
sql/mysqld.cc: WARN_DEPRECATED(NULL, "5.2", "for replication startup options",
sql/set_var.cc: WARN_DEPRECATED(thd, "5.2", "@@table_type", "'@@storage_engine'");
sql/set_var.cc: WARN_DEPRECATED(thd, "5.2", "@@log_bin_trust_routine_creators",
sql/sql_parse.cc: WARN_DEPRECATED(thd, "5.2", buf, "'TIMESTAMP'");
sql/sql_table.cc: WARN_DEPRECATED(thd, "5.2", "BACKUP TABLE",
sql/sql_table.cc: WARN_DEPRECATED(thd, "5.2", "RESTORE TABLE",
sql/sql_yacc.yy: WARN_DEPRECATED(yythd, "5.2", "TYPE=storage_engine",
sql/sql_yacc.yy: WARN_DEPRECATED(yythd, "6.2", "FRAC_SECOND", "MICROSECOND");
sql/sql_yacc.yy: WARN_DEPRECATED(yythd, "5.2", "SHOW PLUGIN", "'SHOW PLUGINS'");
sql/sql_yacc.yy: WARN_DEPRECATED(yythd, "5.2", "SHOW TABLE TYPES", "'SHOW [STORAGE] ENGINES'");
sql/sql_yacc.yy: WARN_DEPRECATED(yythd, "5.2", "SHOW INNODB STATUS", "'SHOW ENGINE INNODB STATUS'");
sql/sql_yacc.yy: WARN_DEPRECATED(yythd, "5.2", "SHOW MUTEX STATUS", "'SHOW ENGINE INNODB MUTEX'");
sql/sql_yacc.yy: WARN_DEPRECATED(yythd, "5.2", "LOAD TABLE FROM MASTER",
sql/sql_yacc.yy: WARN_DEPRECATED(yythd, "5.2", "LOAD DATA FROM MASTER",
This means that the 5.4 version of the server will issue warnings that promise to remove certain features in 5.2. Apparently this is not right.
Actually, the only reason this it works at all is because configure.in states that the version number is 5.1.33-pv-0.2.2. If one changes it to 5.4, one starts getting assertion failures as WARN_DEPRECATED has an assertion that checks for too-late promises.
How to repeat:
See above.
Suggested fix:
Please
- Make 5.4 report correct version number
- Adjust version number in warnings.
