| Bug #34577 | Backup command doesn't error out, if the quotes aren't given for backup location | ||
|---|---|---|---|
| Submitted: | 15 Feb 2008 2:18 | Modified: | 15 Feb 2008 10:00 |
| Reporter: | Hema Sridharan | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S3 (Non-critical) |
| Version: | 6.0.5-alpha-debug | OS: | Linux |
| Assigned to: | CPU Architecture: | Any | |
[15 Feb 2008 10:00]
Susanne Ebrecht
Many thanks for writing a bug report. This is not a bug. It's an expected behaviour. Please read for more informations: http://dev.mysql.com/doc/refman/6.0/en/entering-queries.html Usually, the response is intuitive to Unix/Linux users, because you can find this behaviour at other software too.

Description: In backup command, if quotes are not included in the destination (where backup copy is to be stored), the command doesn't error out instead goes to another prompt (>). User needs to type a quote followed by semicolon to have the command completed or need to abort by pressing CTRL+C.But this is not obvious to the user. How to repeat: create database test, table th, insert few rows in it and take backup. backup database to file test.bak, mysql> backup database test to 'test.bak; '> '> User will get this prompt, unless and until he/she types the quote followed by a semicolon. Command should error out with the specific error code. mysql> backup database test to 'test.bak; '> '> ' -> ; +-----------+ | backup_id | +-----------+ | 11 | +-----------+ 1 row in set (0.06 sec) The response is not intuitive to the end user.