MySQL Bugs: #29530: undocumented options in 'create logfile group' & 'create tablespace' statements

Bug #29530	undocumented options in 'create logfile group' & 'create tablespace' statements
Submitted:	3 Jul 2007 20:15	Modified:	27 Jul 2007 12:59
Reporter:	Sergei Tkachenko	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any
Tags:	undocumented option logfile group tablespace

Description:
At least for 2 statements ('create logfile group' & 'create tablespace') documentation omits several options. See http://dev.mysql.com/doc/refman/5.1/en/create-logfile-group.html http://dev.mysql.com/doc/refman/5.1/en/create-tablespace.html

How to repeat:
Below are excerpts from purified (semantics extracted for simplicity) sql_yacc.yy file, where undocumented options are marked by comments:

logfile_group_option:
  opt_ts_initial_size
| opt_ts_undo_buffer_size
| opt_ts_redo_buffer_size // missing
| opt_ts_nodegroup // missing
| opt_ts_engine
| ts_wait // missing
| opt_ts_comment // missing
;

tablespace_option:
  opt_ts_initial_size
| opt_ts_autoextend_size // missing
| opt_ts_max_size // missing
| opt_ts_extent_size
| opt_ts_nodegroup // missing
| opt_ts_engine
| ts_wait // missing
| opt_ts_comment // missing
;

Suggested fix:
Add appropriate description for each missing option.

Thank you for the report.

Verified as described.

Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php

These options currently don't do anything - note that we don't have any tests for them, either.

Discussed with Sveta, who says since the options don't cause a syntax error, they should be documented as present but having no effect at this time. So that's what will be done.

And so it was done. :) 

(Only the 5.1 & 5.2 versions of the Manual were affected.)

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.