Bug #80838 Column count error when exporting data
Submitted: 23 Mar 2016 13:39 Modified: 28 Apr 2016 11:52
Reporter: Hugo Costa Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL for Windows: MySQL for Excel Severity:S2 (Serious)
Version:1.3.6 OS:Microsoft Windows (8.1)
Assigned to: Assigned Account CPU Architecture:Any

[23 Mar 2016 13:39] Hugo Costa
Description:
This bug occurs on the brazilian version of Excel 2013, with MySQL for Excel 1.3.6.
When exporting data to a new table, i get column count error (MySQL Error 1136).
However, if i uncheck the "First Row Contains Columns Names" checkbox, the data is exported successfully.
From what i learned, the cause is the decimal separator used in my region.
When previewing the SQL Query, the values are not enclosed with ' when the "First Row Contains Columns Names" is checked.

How to repeat:
Using the brazilian version of Excel 2013, select the data you want exported, click on the "Export Data to a New Table" button, make sure you leave the "First Row Contains Columns Names" checkbox marked, and then click Export Data.

Suggested fix:
Enclose the values with ', when the "First Row Contains Columns Names" checkbox is marked.
[23 Mar 2016 13:48] Hugo Costa
SQL Query showing values are not enclosed with '

Attachment: MySQLForExcelBug.png (image/png, text), 121.12 KiB.

[28 Mar 2016 11:52] Chiranjeevi Battula
Hello Hugo Costa,

Thank you for the bug report.
I tried to reproduce the issue at my end using MS Excel 2013, Windows 8.1,  MySQL for Excel 1.3.6 but not seeing any issues with exporting data.
Could you please provide repeatable test case (sample excel data etc. - please make it as private if you prefer) to confirm this issue at our end?

Thanks,
Chiranjeevi.
[28 Mar 2016 11:53] Chiranjeevi Battula
Screenshot.

Attachment: 80838.JPG (image/jpeg, text), 110.31 KiB.

[29 Apr 2016 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".