Bug #86132 (Empty Table) Error Code: 2013. Lost connection to MySQL server during query
Submitted: 28 Apr 2017 13:43 Modified: 30 Sep 2017 22:48
Reporter: Vincent DeCampo Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3 OS:Linux
Assigned to: CPU Architecture:Any

[28 Apr 2017 13:43] Vincent DeCampo
Description:
A 'Select *' query from empty table fails with error code 2013. Other tables query just fine. Tried dropping and recreating table. Same result. Previous iterations of database schema run fine. Only difference is the database name. However, if you select to query the Column name directly, that query works.

How to repeat:
CREATE TABLE `technician` (
  `TechName` varchar(255) NOT NULL,
  PRIMARY KEY (`TechName`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

SELECT TechName
FROM commanddb_swosgreatlakes.technician; //WORKS

SELECT * FROM commanddb_swosgreatlakes.technician; // FAILS Error 2013
[28 Apr 2017 13:48] Vincent DeCampo
This error occurs in MySQL Workbench. The database queries fine from my code.
[28 Apr 2017 13:51] Vincent DeCampo
Updated Version number.
[28 Apr 2017 18:29] MySQL Verification Team
Thank you for the bug report. Please provide the complete version 6.3.X, the Linux OS and the MySQL Server version. Thanks.
[1 May 2017 15:50] Vincent DeCampo
MySQL Version 5.5.43-37.2-log Percona Server (GPL), Release rel30.2, Revision 38.2 

MySQL Workbench Version 6.3.8 Build 1228 CE (64 bits) Community
[8 May 2017 22:03] MySQL Verification Team
Please try version 6.3.9. Thanks.
[9 May 2017 12:36] Vincent DeCampo
Exact same issue with 6.3.9. If I select the table and click the icon to select the first 1000 rows, it times out. If I go to the column and query it, the query works.
[30 Aug 2017 22:48] MySQL Verification Team
Thank you for the feedback and sorry for my delay. Which is your Linux OS version, the WorbBench is Linux version, Windows, MAC OS X?, your connection is local or remote?. Thanks in advance.
[1 Oct 2017 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".