Bug #70798 mysqldump won't dump routines to --tab
Submitted: 1 Nov 2013 21:03 Modified: 8 Nov 2013 18:17
Reporter: Joe Brown Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.1.71, 5.5.35, 5.6.15 OS:Any
Assigned to: Assigned Account CPU Architecture:Any
Tags: mysqldump routines

[1 Nov 2013 21:03] Joe Brown 
Description:
mysqldump -u <user> -p --no-data --opt --routines --tab=<folder> <database>

this does not dump routines, only tables.

How to repeat:
mysqldump -u <user> -p --no-data --opt --routines --tab=<folder> <database>

Suggested fix:
routines should be separably scriptable when using the --tab option.
[2 Nov 2013 13:35] Peter Laursen 
Actually documentation does not tell anything about it!
Refer http://dev.mysql.com/doc/refman/5.6/en/mysqldump.html#option_mysqldump_tab

It is only listed how table structure/DDL and data/DML are handled.  No information about other types of database objects (routines, triggers, events, views). I personally think it would make sense to have one or .sql files written with DDL information about all those.  If not, then at least docs should mention that --tab option ignores all non-table objects.

Peter
(not a MySQL/Oracle person)
[7 Nov 2013 20:00] Sveta Smirnova 
Thank you for the report.

Routines are actually dumped, but not in the file table_name.sql, but to stdout. But our user manual could mention this. So verified as a doc request.
[8 Nov 2013 18:17] Sveta Smirnova 
After internal discussion we decided this is server bug and actually a duplicate of already reported more general case: bug #51167