myloader: wrong database name in message when -B used
Bug #1440437 reported by
Charles Thompson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL Data Dumper |
Fix Released
|
Low
|
Max Bubenick | ||
Bug Description
Hello,
When -B is used for an alternate database name to restore into, the "Restoring Triggers" and "Restoring routines and events" message has the wrong database name specified. It still restores to the correct database but the message isn't right which is misleading.
Example:
testing123 is used for -B parameter. Views work fine but triggers and routines/events do not
** Message: Dropping table or view (if exists) `testing123`
** Message: Creating table `testing123`
** Message: Restoring triggers for `resources`
** Message: Restoring routines and events for `resources`
| Changed in mydumper: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| assignee: | nobody → Max Bubenick (max-bubenick) |
| milestone: | none → 0.9.1 |
| status: | Triaged → Fix Committed |
Revision history for this message
| Charles Thompson (01charles-t) wrote | #1 |
| Changed in mydumper: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thanks Max!