[MDEV-15021] mysqldump --tables --routines generates non importable dump file - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 5.5, 10.0, 10.1, 5.5.56, 10.2, 10.2.8
Fix Version/s: 5.5.61, 10.0.36, 10.1.34, 10.2.16, 10.3.8
Component/s: Scripts & Clients
Labels:
Environment:
Mac OS X 10.13.2, CentOS 7.4.1708

Description

When exporting some views and routines together (to separate manually and automatically managed parts of a schema) with `mysqldump ... --routines --tabels table1 table2 ...` I noticed that the generated dump-file is not importable again, because the routines are ordered after all the tables/ views and thus views that use them cannot be imported.

I have attached a test dump that I generated that shows this problem.

Workaround: Using negative logic and instead listing all the tables/views to skip seems to not trigger this bug.

Attachments

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

Attachments

problematic_dump.sql
6 kB
2018-01-22 08:58

Issue Links

links to

pr 693

Activity

People

Assignee:: Rutuja Surve (Inactive)

Reporter:: Martin Häcker

Votes:: 1 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2018-01-22 08:58

Updated:: 2018-06-10 13:56

Resolved:: 2018-06-10 13:56

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.