MySQL Bugs: #45349: Backup documentation does not mention when backup will abort

Bug #45349	Backup documentation does not mention when backup will abort
Submitted:	5 Jun 2009 13:03	Modified:	10 Jun 2009 17:19
Reporter:	Jørgen Løland	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	6.0	OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
The MySQL documentation for the new Backup feature does not mention that backup will abort if it encounters schema objects that are "illegal" (in lack of better words) in the database it backs up. An example where backup errors can be seen in BUG#44283.

How to repeat:
RTM

Suggested fix:
Add a sentence or two that "backup database" will give up if it encounters schema objects that are illegal.

"Illegal" is pretty vague. Do you have other examples of what this might mean other than the one in the referenced bug report?

I'm currently not aware of any other concrete examples, but any object that would fail to be created will have the same problem.

There is a related issue during RESTORE - bug#44283

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.

Added this note to
http://dev.mysql.com/doc/refman/6.0/en/backup-database.html:

A backup operation fails with an error if it encounters objects that
are illegal. For example, this occurs for a view for which an 
underlying table has been dropped or altered in such a way that the
view definition has become invalid.  

And added a similar note to
http://dev.mysql.com/doc/refman/6.0/en/restore.html.