Bug #44864 dump only views
Submitted: 14 May 2009 9:01 Modified: 14 May 2009 9:03
Reporter: Susanne Ebrecht Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: Command-line Clients Severity:S4 (Feature request)
Version:5.0, 5.1, 6.0 OS:Any
Assigned to: CPU Architecture:Any

[14 May 2009 9:01] Susanne Ebrecht
Imagine a huge instances (let us say 200 schemas with 100 tables and lots of views, triggers, routines each) needs to be dumped because of backup or upgrade reasons.

You want to use mysqldump here by storing in a file.

Of course you don't want to get all in only one file.

By running it twice: once time with --no-create-info and the other time with --no-data you will get two files: one without data and one with only data.

But that is also to complex. You want a dump without data but you want to get a separate file for triggers, a separate file for routines and a separate file for views.

For triggers and routines this also is possible by using:
mysqldump --no-create-info --no-data --triggers -A (for only triggers)
mysqldump --no-create-info --no-data -R -A (for only routines)

What is missing?

Missing is a possibility to dump only views.

Something like:
mysqldump --no-create-info --no-data --views -A

How to repeat:
It is a feature request

Suggested fix:
Add an option that allows to switch on/off Views that is on by default.
[19 May 2009 7:39] Sveta Smirnova
There is bug #44939 which shows a problem with current behavior.