Bug #81185 Display formatting critique

Submitted: 23 Apr 2016 19:01 Modified: 25 Apr 2016 6:39
Reporter: Rick James Email Updates:
Status: Won't Fix 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] MySQL Verification Team
Hello Rick James,

Thank you for the report and feedback.

Thanks,
Umesh
[14 Sep 18:03] Omer Barnir
Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.