Bug #48895 have ability avoid warning for _correct_ deprecated option
Submitted: 19 Nov 2009 9:38
Reporter: Andrii Nikitin Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Options Severity:S4 (Feature request)
Version: OS:Any
Assigned to: CPU Architecture:Any

[19 Nov 2009 9:38] Andrii Nikitin
When some option becomes the only possible behavior (thus disappears), it is marked deprecated.

It is not good that user is getting warning when uses this option because of two reasons:
1. there is nothing bad in using such option (i.e. we use default behavior in next version)
2. there is no way to suppress the warning 

How to repeat:
This problem exists at least for following options:


Suggested fix:
We should provide some way to eliminate warnings for using such options.

If deprecated option is the only behavior in future releases, and used with "deprecated" prefix we should write no warning on startup:

so if server started with "deprecated" prefix on option, this means option is valid but no warning is printed.

So, --deprecated-skip-thread-priority is the same as --skip-thread-priority but without warning printed.

(technically we can apply this for all options so "deprecated" prefix will mean owner is aware that option will disappear and removed all dependencies)