Bug #74788 | Table Inspector - Analyze Table fails | ||
---|---|---|---|
Submitted: | 11 Nov 2014 10:35 | Modified: | 19 Sep 2015 0:37 |
Reporter: | Brett Pit | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
Version: | 6.2.3 | OS: | Windows (7) |
Assigned to: | CPU Architecture: | Any | |
Tags: | inspector |
[11 Nov 2014 10:35]
Brett Pit
[11 Nov 2014 10:40]
MySQL Verification Team
Hello Brett Pit, Thank you for the report and steps. Thanks, Umesh
[11 Nov 2014 10:43]
MySQL Verification Team
How to repeat: - Create below schema create database `bug-74788`; use `bug-74788`; create table t1(id int not null); - Right click on table 't1'->Table Inspector -> Analyze table to trigger the exception.
[19 Sep 2015 0:37]
Philip Olson
Fixed as of the upcoming MySQL Workbench 6.3.5 release, and here's the changelog entry: The Table Inspector could fail if the schema name contained a dash. Thank you for the bug report.