Invalid syntax created if mysqldump run with option --where="NEWLINE condition"
Bug #1584021 reported by
Sveta Smirnova
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL Server |
Unknown
|
Unknown
|
||||
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.5 |
Triaged
|
Medium
|
Unassigned | |||
| 5.6 |
Triaged
|
Medium
|
Unassigned | |||
| 5.7 |
Triaged
|
Medium
|
Unassigned | |||
Bug Description
Description:
If I run mysqldump with option WHERE, but put part of it on new line resulting output would be invalid SQL:
./bin/mysqldump -uroot -S /tmp/sveta56.sock --where="\
> user='root'" mysql user
...
--
-- Dumping data for table `user`
--
-- WHERE:
user=root
How to repeat:
./bin/mysqldump -uroot -S /tmp/sveta56.sock --where="\
> user='root'" mysql user
Suggested fix:
Comment parts of WHERE clause even if they are on the new line
| tags: | added: upstream |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/