MySQL Bugs: #61046: Docs bugs: sysvar_innodb_flush_log_at_trx_commit

Bug #61046	Docs bugs: sysvar_innodb_flush_log_at_trx_commit - s/numeric/enumeration/, etc.
Submitted:	3 May 2011 23:34	Modified:	8 Nov 2011 23:17
Reporter:	Morgan Tocker	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.5	OS:	Any
Assigned to:	John Russell	CPU Architecture:	Any

Description:
Bug #1:

See: http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_flush_log_at_t...

I think someone people often get confused between 0, 1 & 2.  Since 2 does not imply one, I think it should not be "numeric", but an "enumeration" of options?

Bug #2:

See: http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_force_recovery

I might argue innodb_force_recovery is actually a numeric, since each number implies the previous.

(I am less concerned if you want to leave this as-is.  Fewer people are confused by this setting / it's less dangerous if you do not change.)

How to repeat:
See above.

Suggested fix:
See above above.

Thank you for the bug report.

Both options could arguably be classified either way, because the restricted set of numbers is like an enumeration, but syntactically it's useful to know that the argument has to be numeric. I've made them both "enumeration" for consistency.