Bug #91576 | Exporting to excel .xml files on any substantial size not working | ||
---|---|---|---|
Submitted: | 9 Jul 2018 12:37 | Modified: | 10 Jul 2018 14:24 |
Reporter: | Christopher Naviaux | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 6.3.10 | OS: | Windows (Microsoft Windows 10 Enterprise) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[9 Jul 2018 12:37]
Christopher Naviaux
[9 Jul 2018 12:41]
Christopher Naviaux
log file
Attachment: 5C43F461.log (application/octet-stream, text), 191 bytes.
[10 Jul 2018 7:01]
Chiranjeevi Battula
Hello Christopher, Thank you for the bug report. This is most likely duplicate of Bug #67092, please see Bug #67092 Thanks, Chiranjeevi.
[10 Jul 2018 14:24]
Christopher Naviaux
Chiranjeevi, This is not a duplicate of 67092. 67092 is simply stating that they are not getting .xls files and are only able to export to .xml. This bug is that the .xml export is "corrupt" and will not open in excel. The error log is copied in the original report as well as added as an attachment. I am not needing the export to be in .xls (or xlsx) I am reporting that once a file gets very large at all, the excel spreadsheet .xml will no longer open in excel. .JSON export works with an import into excel; however, that is a much longer roundabout way to get at the data.
[7 Nov 2023 18:48]
Darren Oliver
so 5 years later an nothin huh? this still is an issue.