drizzledump --databases option does not appear to work
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
Medium
|
Andrew Hutchings | ||
| 7.0 |
Fix Released
|
Medium
|
Andrew Hutchings | ||
Bug Description
When we attempt to use Drizzledump this way:
drizzledump [OPTIONS] –databases [OPTIONS] DB1 [DB2 DB3...]
it appears that nothing is being migrated. The program is called and returns with no output, but neither of the two databases from my test are transferred.
If I attempt to migrate the databases individually --destination-
To repeat, attempt to run the following:
./test-run --suite=
You will observe that the test will fail due to the first expected database not being present in Drizzle.
drizzletest: At line 55: query 'SELECT * FROM $database1.t1' failed: 1146: Table 'drizzledump_
How we call drizzledump with this option.
../client/
Related branches
- Lee Bieber (community): Needs Fixing
-
Diff: 138 lines (+20/-21)5 files modifiedclient/drizzledump.cc (+5/-6)
client/drizzledump_data.cc (+5/-0)
client/drizzledump_data.h (+1/-0)
client/drizzledump_drizzle.cc (+2/-2)
client/drizzledump_mysql.cc (+7/-13)
| Changed in drizzle: | |
| assignee: | nobody → Andrew Hutchings (linuxjedi) |
| status: | New → Confirmed |
| Changed in drizzle: | |
| assignee: | Andrew Hutchings (linuxjedi) → Patrick Crews (patrick-crews) |
| status: | Confirmed → In Progress |
| Patrick Crews (patrick-crews) wrote | #1 |
| Changed in drizzle: | |
| assignee: | Patrick Crews (patrick-crews) → Andrew Hutchings (linuxjedi) |
| status: | In Progress → Confirmed |
| Patrick Crews (patrick-crews) wrote | #2 |
There was an error in the test case - was reverifying.
After fixing the test I am still seeing this problem. The expected tables are on the MySQL server, but they are not making it to Drizzle. drizzledump runs silently when called.
../client/