Bug #72611 | Error during "Execute Query Into Text Output" | ||
---|---|---|---|
Submitted: | 11 May 2014 13:18 | Modified: | 25 Aug 2014 19:16 |
Reporter: | David Hemming | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S5 (Performance) |
Version: | 6.1.4 | OS: | Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 build 7601, 64-bit) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[11 May 2014 13:18]
David Hemming
[11 May 2014 13:19]
David Hemming
Log File
Attachment: wb.log (application/octet-stream, text), 10.42 KiB.
[25 Aug 2014 19:16]
Philip Olson
Fixed as of the upcoming MySQL Workbench 6.2.2 release, and here's the changelog entry: Executing "Execute (All or selection) to Text" on queries that SELECT from empty tables would fail and generate an error similar to "Error during "Execute Query Into Text Output" error calling Python module function SQLIDEUtils.executeQueryAsText". Thank you for the bug report.