Bug #45906 mysqldump --ignore-table: OK to specify tables that might not exist
Submitted: 2 Jul 2009 11:43 Modified: 22 Aug 2009 16:35
Reporter: Dan Jacobson Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S5 (Performance)
Version: OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[2 Jul 2009 11:43] Dan Jacobson 
Description:
On the mysqldump man page it only says

       o  --ignore-table=db_name.tbl_name

          Do not dump the given table, which must be specified using
          both the database and table names. To ignore multiple tables,
          use this option multiple times. This option also can be used
          to ignore views.

How to repeat:
...

Suggested fix:
Also mention that is not an error if one specifies a table or database that
does not exist. That specification will be silently ignored.
[2 Jul 2009 12:30] Valeriy Kravchuk 
Thank you for the documentation request.
[3 Jul 2009 23:49] Dan Jacobson 
Wait, for older versions, e.g., 5.0.32. This will cause an error message and the dump will fail. So better mention that too...
[9 Jul 2009 16:43] Paul DuBois 
"Wait, for older versions, e.g., 5.0.32. This will cause an error message
and the dump will fail. So better mention that too..."

"This" = what?
[9 Jul 2009 16:50] Dan Jacobson 
If the user uses
mysqldump --ignore-table db_name.a_table_that_does_not_exist
newer versions will silently ignore it,
but not older versions.
[21 Aug 2009 19:14] Paul DuBois 
I tried: mysqldump --ignore-table=test.notable test

I don't get an error for any version. Can you provide a test case?

On the other hand, if I try this: mysqldump --ignore-table=test.notable test notable

I get an error for all versions. Perhaps this is a bug, although I suppose you could said it doesn't make sense to both specify that you want a table dumped and that you don't.
[22 Aug 2009 2:13] Dan Jacobson 
Well, OK, I suppose one should mainly document current behavior... So welcome to close this bug if you want.