Bug #80407 | MySQL for Excel - table was not created due to errors on rows insertion | ||
---|---|---|---|
Submitted: | 17 Feb 2016 12:32 | Modified: | 15 Apr 2016 15:46 |
Reporter: | Revathi Rangachari | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL for Windows: MySQL for Excel | Severity: | S3 (Non-critical) |
Version: | 1.3.6 | OS: | Windows (Windows 7 Professional -64-bit OS) |
Assigned to: | CPU Architecture: | Any | |
Tags: | MS Office Excel 2007, MySQL for Excel - 1.3.6 |
[17 Feb 2016 12:32]
Revathi Rangachari
[18 Feb 2016 6:59]
Chiranjeevi Battula
Hello Revathi Rangachari, Thank you for the bug report. Verified this behavior on MS Excel 2013, MySQL for Excel 1.3.6. Thanks, Chiranjeevi
[18 Feb 2016 6:59]
Chiranjeevi Battula
Screenshot.
Attachment: 80407.PNG (image/png, text), 197.41 KiB.
[15 Apr 2016 15:46]
Javier TreviƱo
Posted by developer: This is not a bug. As per design, the automatic detection of data types for Export Data operations is capped at 1000 rows, intentionally. This is because analyzing more than that would require a lot of time and many users may complain about that process being slow. The data detection is just a suggestion as close as possible to reality for the data types. The data type can be manually adjusted in case the export fails, so in the example given in this bug report, the varchar length could have been easily adjusted in the Data Type combo box to add one more character to the lenght, or as many as needed. The suggested fix is not good because it violates the reason I mentioned before for the data detection to be designed this way.