Bug #49442 | Unable to view full queries from logs | ||
---|---|---|---|
Submitted: | 4 Dec 2009 3:59 | Modified: | 9 Feb 2010 10:30 |
Reporter: | Todd Farmer (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
Version: | 5.2.10 r4680 | OS: | Windows (XP) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[4 Dec 2009 3:59]
Todd Farmer
[4 Dec 2009 4:00]
Todd Farmer
Screenshot
Attachment: SP32-20091203-200005.gif (image/gif, text), 71.68 KiB.
[28 Jan 2010 13:35]
Alfredo Kojima
We should make it so that dbl-clicking the row or clicking a [View Selected] button pops up a window with the full contents of the row.
[28 Jan 2010 14:15]
Todd Farmer
Please also ensure that the query or contents may be copied, whatever the final decision on solution is.
[28 Jan 2010 22:10]
Alfredo Kojima
I've added a Copy Detail button that copies the contents of the detail/SQL field into the clipboard.
[1 Feb 2010 14:48]
Johannes Taxacher
fix will be included in 5.2.16
[9 Feb 2010 10:30]
Tony Bedford
A 'change' entry has been added to the 5.2.16 changelog: In the Logs tab of the Administrator it was not possible to view long queries, or copy their text. MySQL Workbench has been changed so that double-clicking on an entry in the Logs tab pops up a dialog with the complete text, and also provides a Copy Detail button to copy the text of the entry.