| Bug #74057 | Semicolons used in values cause problems in queries sent to MySQL server | ||
|---|---|---|---|
| Submitted: | 24 Sep 2014 18:30 | Modified: | 10 Oct 2014 4:35 |
| Reporter: | Javier Treviño | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL for Windows: MySQL for Excel | Severity: | S2 (Serious) |
| Version: | 1.2.0 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[3 Oct 2014 1:34]
Javier Treviño
Posted by developer: Fixed the way a previewed SQL script is split into individual SQL statements using a tokenizer that detects each type of token within the script text, so now the delimiters for SQL statements are detected correctly.
[10 Oct 2014 4:35]
Philip Olson
Posted by developer:
Fixed as of the upcoming MySQL for Excel 1.3.3 release, and here's the changelog entry:
Using semicolons (';') in values like schema names, column names or text
values caused SQL queries sent to the MySQL server to fail. Internally,
MySQL for Excel treated the semicolon as a separator for SQL statements.
Thank you for the bug report.
Description: Using semicolons (';') in values like schema names, column names or text values cause a problem in the SQL queries sent to the MySQL server. Internally MySQL for Excel treats the semicolon as a separator for SQL statements. How to repeat: 1. Open MySQL for Excel 2. On the schema selection panel click "Create New Schema" 3. Give a schema name containing a semicolon (e.g. "my;schema") and click OK. Note an error is thrown stating the SQL is malformed and should be checked. 4. Select any table that contains varchar or text columns and click "Edit MySQL Data" 5. Type in a text value containing a semicolon, click "Commit Changes". 6. Note again that an error is thrown stating the SQL text has problems. Suggested fix: A better job at tokenizing the SQL statements must be done.