MySQL Bugs: #53728: myqldump --no-tablespaces not documented

Bug #53728	myqldump --no-tablespaces not documented
Submitted:	18 May 2010 7:01	Modified:	24 May 2010 15:29
Reporter:	Geert Vanderkelen	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	mysql-5.1+	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any
Tags:	Docs, mysqldump

Description:
The mysqldump option --no-tablespaces is not documented.

It was introduced in MySQL 5.1.14 with a patch for bug #20839.

How to repeat:
Using latest MySQL 5.1.46:
shell> mysqldump --help | grep -- --no-tablespaces
  -y, --no-tablespaces

That option is not found on:
  http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html

Suggested fix:
--no-tablespaces should be used when you do not want any CREATE LOGFILE GROUP or CREATE TABLESPACE in the dump generated by mysqldump. (see bug #53108)
The --no-create-info is not enough in this case, as logfile groups and tablespace create statements are dumped as soon as there is at least 1 (NDB) table using Disk-Based storage. (see bug #53109)

For example, if you _only_ want to dump the stored routines for a particular database and you have at 1 NDB table, you need to do this:
  mysqldump --no-create-info --no-tablespaces --routines dbname

Corrected Category.

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.