MySQL Bugs: #64240: Workbench is crashed if it is set table alias with SELECT *

Bug #64240	Workbench is crashed if it is set table alias with SELECT *
Submitted:	6 Feb 2012 13:24	Modified:	28 Mar 2012 20:13
Reporter:	Oleg Preobrazhenskyy	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	5.2.37	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
WB is crashed while executing such a query.

Example,

SELECT cron.* FROM ilance_cron AS cron

It does not if do not use alias.

SELECT * FROM ilance_cron AS cron

How to repeat:
CREATE table ilance_cron(x text);

SELECT cron.* FROM ilance_cron AS cron

In first message I pasted not right table;
This one is right:

CREATE TABLE `ilance_cron` (
  `cronid` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `nextrun` int(10) unsigned NOT NULL DEFAULT '0',
  `weekday` smallint(6) NOT NULL DEFAULT '0',
  `day` smallint(6) NOT NULL DEFAULT '0',
  `hour` smallint(6) NOT NULL DEFAULT '0',
  `minute` varchar(100) NOT NULL DEFAULT '',
  `filename` char(50) NOT NULL DEFAULT '',
  `loglevel` smallint(6) NOT NULL DEFAULT '0',
  `active` smallint(6) NOT NULL DEFAULT '1',
  `varname` varchar(100) NOT NULL DEFAULT '',
  `product` varchar(200) NOT NULL DEFAULT '',
  PRIMARY KEY (`cronid`),
  UNIQUE KEY `varname` (`varname`),
  KEY `nextrun` (`nextrun`),
  KEY `product` (`product`),
  KEY `active` (`active`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

And the query who do the crash is:

SELECT cron.* FROM ilance_cron AS cron

I can not repeat this on Mac OS X while working with local MySQL server 5.5.20. What exact OS do you run Workbench on and what exact server version are you working with?

OS: Windows 7 ultimate x64
Server version: 5.5.16-log MySQL Community Server (GPL)

Thank you for the bug report. Verified on Windows 7 Ultimate 64-bit.

Call Stack

Attachment: wb_call_stack.txt (text/plain), 16.52 KiB.

Thanks for your report Oleg.
This has been fixed in the new WB 5.2.38, can you please download it and confirm the fix?
Thanks.

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