Bug #25153 mysqld --skip-engine option
Submitted: 18 Dec 2006 17:35 Modified: 19 Dec 2006 8:52
Reporter: Peter Gulutzan Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Options Severity:S3 (Non-critical)
Version:5.0,5.1 OS:Linux (SUSE 10.0 / 64-bit)
Assigned to: CPU Architecture:Any
Triage: Triaged: D4 (Minor)

[18 Dec 2006 17:35] Peter Gulutzan
Description:
There is a new mysqld option --skip-engine=(engine name), e.g.
mysqld --skip-engine=innodb
does not return an error message.

But it's not documented in the place I'd expect,
http://dev.mysql.com/doc/refman/5.1/en/server-options.html

And it doesn't work.

How to repeat:
Start mysqld with
--skip-engine=innodb

On mysql client, say:
show engines;

The engine will be there, enabled.
[18 Dec 2006 19:24] Valeriy Kravchuk
Thank you for a problem report. It is either a bug or, at least, a dicumentation request. Verified just as described with 5.0.32-BK and 5.1-15-BK.
[8 Jan 2007 20:32] Sergei Golubchik
It's documented here:
http://dev.mysql.com/doc/refman/5.1/en/program-options.html
"
 An option can be specified by writing it in full or as any unambiguous prefix. For example, the --compress  option can be given to mysqldump as --compr, but not as --comp  because that is ambiguous
"
here:
http://dev.mysql.com/doc/refman/5.1/en/command-line-options.html
"
Some options control behavior that can be turned on or off. For example
...
--skip-column-names
"

and here:
http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html
"
 engine_condition_pushdown
"

So by writing --skip-engine you're disabling engine-condition-pushdown by its unambiguous prefix.
[8 Jan 2007 20:35] Sergei Golubchik
still, one should not be allowed to write

  --skip-boolean-option=arbitrary-string