Bug #76223 MySQL Workbench - Can't export full query
Submitted: 9 Mar 2015 11:40 Modified: 11 Dec 2015 2:26
Reporter: Johann Wurm Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.1 OS:Windows (Microsoft Windows 8.1 Enterprise N)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[9 Mar 2015 11:40] Johann Wurm 
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\Johann\AppData\Roaming\MySQL\Workbench\log\wb.log]

In Statement Analysis you see all queries but queries will be truncated. You can't copy the whole query. With export this is also not working. So I can't find the correct query.

How to repeat:
1. Open Connection to a MySQL Server
2. Go to Performance Reports
3. Click on High Cost SQL Statements -> Statement Analysis
4. If you "Copy Selected" and there is a long query then you get a truncated query and not the original query.
[9 Mar 2015 15:30] MySQL Verification Team 
Thank you for the bug report.
[17 Jun 2015 0:20] Philip Olson 
Posted by developer:
 
Where is this information displayed?  I believe it's only available from the "Options File" page now, right? Could it be displayed (and edited) from "Performance Schema Setup"? I think that'd be useful, especially considering how there are multiple variables involved (and changes depending on the MySQL server version).
[17 Jun 2015 6:06] Johann Wurm 
Copy Selected in Performance Reports

Attachment: Workbench - cannot get query.PNG (image/png, text), 112.64 KiB.
[17 Jun 2015 6:10] Johann Wurm 
I've attached a screenshot.
Steps:
1. Click on Performance Reports
2. Click on High Cost SQL Statements -> Statement Analysis
3. Select a very long query
4. Click on "Copy Selected"
5. Paste it in a Text Editor
6. Like on screenshot you see a part of the query - ends up with "..."

Query is cutted in the middle, so I can't see the whole query and the importand WHERE - parameters (variables).
[17 Jun 2015 11:07] Philip Olson 
Hello Johann, thank you for the information. That part is known and
intentional, as the size limit is controlled by the MySQL server and not
MySQL Workbench. However, I'm wondering if Workbench could clarify that there
is a size limit, what it is, and how to change it.
[11 Dec 2015 2:26] Philip Olson 
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.3.6 release, and here's the changelog entry:

The performance_schema_max_sql_text_length and max_digest_length options
were not displayed under the Options File tab. These variables dictate how
queries under Statement Analysis are truncated.

Thank you for the bug report.