Bug #81185 Display formatting critique
Submitted: 23 Apr 2016 19:01 Modified: 25 Apr 2016 6:39
Reporter: Rick James Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:6.3.5, 6.3.6 OS:Any
Assigned to: CPU Architecture:Any
Tags: formatting

[23 Apr 2016 19:01] Rick James
Description:
Looking at "Performance Reports":

* Put thousands separators in numbers to make them readable.  (Even for India, use 3-digit clumps at least for microsecond/nanosecond numbers.)
* Switch to K/M/... suffix when the number won't fit in the allowed space.  (The current formatting is _useless_:  "123456...".)
* When clicking on a heading, sort DESC _first_ -- after all, the biggies are usually what someone is looking for.
* Wrap headings into 2 lines if not enough space.
* If practical, interrogate display size and provide more space for first column (file/query/etc)
* "Pivot" 'Schema Object Overview' table on ObjectType
* In 'Unused Indexes', state datetime when collection started.

How to repeat:
Bring up Workbench's "Performance Reports"

Suggested fix:
(see Description)
[25 Apr 2016 6:39] Umesh Shastry
Hello Rick James,

Thank you for the report and feedback.

Thanks,
Umesh