MySQL Bugs: #55163: Queries do not run

Bug #55163	Queries do not run
Submitted:	11 Jul 2010 11:15	Modified:	12 Aug 2010 11:59
Reporter:	Elija Goldman	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	V5.2.25	OS:	Linux (64bit Ubuntu deb install)
Assigned to:		CPU Architecture:	Any
Tags:	queries fail, sql editor

Description:
Many queries fail to execute in SQL editor. This in my weekend of use happened to between 30 and 40 percent of queries. No indication of a failure or error message is given.

How to repeat:
Open SQL Editor
Select a database
Right click a table
Choose "Select rows - limit 1000"

Had you tried to find out something about the tables for which queries do not run? Maybe they all use the same storage engine or something like that.

All the tables are INNODB. 
They are currently very small in terms of number of rows (between 2 and 10).
They may or may not have foreign keys.
Apart from the primary keys (autonumber fields) there are no other indexes.

Example table where the problem has occurred:

CREATE TABLE  `Fifth`.`SessionData` (
  `uid` varchar(64) NOT NULL,
  `host` varchar(512) NOT NULL,
  `sessionTime` datetime NOT NULL,
  `sessionStart` datetime NOT NULL,
  `sessionlocked` char(1) NOT NULL,
  `sessionData` text NOT NULL,
  `userAgent` varchar(1024) NOT NULL,
  `userID` int(11) DEFAULT NULL,
  PRIMARY KEY (`uid`),
  KEY `fk_SessionData_Users` (`userID`),
  CONSTRAINT `fk_SessionData_Users` FOREIGN KEY (`userID`) REFERENCES `Users` (`uid`) ON DELETE NO ACTION ON UPDATE NO ACTION
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Can you try to run:

select * from `SessionData` limit 1000;

from mysql command line client (or some other tool besides Workbench) connected to the same server and database. I need to know if it gives you expected results.

The query works fine in the mysql command line client and in query browser. In fairness it is currently running OK in workbench as well. I suspect I had some something else as well to trigger the condition. I am sorry but I have no idea what that might have been. 

If I can replicate it again, I will of course post back.

Please, inform us about any ideas on how to repeat this bug.

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".