MySQL Bugs: #52722: MySQL Workbench: SQL Editor Crashes When Applying Update

Bug #52722	MySQL Workbench: SQL Editor Crashes When Applying Update
Submitted:	9 Apr 2010 14:27	Modified:	16 Apr 2010 15:31
Reporter:	Neil	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.17	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	crashes, editor, MySQL, SQL, workbench

Description:
We are running version 5.2.17 of MySQL Workbench.  Our connection is over SSH.  When using the SQL Editor to update a table with a basic UPDATE commmand, the application freezes.  The only option is to end the task.

As a result it appears to hang our MySQL 5 server - and we can't even stop the MySQL service.  We need to reboot the machine to end the MySQL service.

Has anyone else seen this issue ?

Cheers
Neil

How to repeat:
Open MySQL Workbench 5.2.17 SQL Editor (over SSH) run a update command.

Does it happen with any update or only with specific one? Please, send the exact UPDATE statement that leads to this problem.

I'm trying to apply a very basic update like

UPDATE Properties SET Name = 'My Property Name' WHERE PropertiesID = 1255

Please, send the results of

SHOW CREATE TABLE Properties\G

just for completeness.

This is the result of my query

       Table: AccMaster
Create Table: CREATE TABLE `AccMaster` (
  `MasterID` int(10) unsigned NOT NULL DEFAULT '0',
  `AccName` varchar(50) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `Street` varchar(50) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `Town` varchar(30) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `County` varchar(30) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `PostalCode` varchar(30) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `Country` varchar(30) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
  `Enabled` char(3) COLLATE utf8_unicode_ci NOT NULL DEFAULT 'No',
  `Rating` tinyint(3) unsigned NOT NULL DEFAULT '0',
  `Longitude` double NOT NULL DEFAULT '0',
  `Latitude` double NOT NULL DEFAULT '0',
  `Distance` double NOT NULL DEFAULT '0.1',
  `Ranking` int(10) unsigned NOT NULL DEFAULT '0',
  `Category` varchar(64) COLLATE utf8_unicode_ci DEFAULT NULL,
  `ThumbnailPhotoURL` varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL,
  `PreferredHotel` char(3) COLLATE utf8_unicode_ci DEFAULT 'No',
  `RateGuarantee` char(3) COLLATE utf8_unicode_ci DEFAULT 'No',
  `PriceFrom` double DEFAULT '0',
  PRIMARY KEY (`MasterID`),
  FULLTEXT KEY `idx_CountryCountyAccName` (`AccName`,`County`,`Country`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci      

Let me know if you need further information.

We were discussing  Properties table (used in UPDATE that crashed SQL Editor), but you sent CREATE TABLE for the different table. Why?

I want to check if this UPDATE can run for a long time because of no index used and/or huge table.

Sorry the intial update statement was a sample with made update field name however the statement was the same. The attached create table information was taken from the CREATE TABLE properties\G command tou asked me to run. My table has about 4500 records with the index as described. Sorry for the confusion.

Some additional information that when I apply a update using the visual editor the application hangs too not just when applying a written UPDATE statement

For your information - I just upgraded to version mysql-workbench-oss-5.2.18-beta-win32.msi and my update statements appear to be working OK now ??

Not repeatable with recent version of MySQL Workbench, 5.2.18.