Bug #64051 | MySQL WorkBench crash while query is running | ||
---|---|---|---|
Submitted: | 17 Jan 2012 13:42 | Modified: | 27 Mar 2012 1:59 |
Reporter: | Oleg Preobrazhenskyy | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S1 (Critical) |
Version: | 5.2.37 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[17 Jan 2012 13:42]
Oleg Preobrazhenskyy
[17 Jan 2012 14:23]
Valeriy Kravchuk
I have no crash with this query on Windows XP when I work with local MySQL server 5.1.58. What server version do you work with, and on what exact OS do you run Workbench?
[18 Jan 2012 10:13]
Oleg Preobrazhenskyy
OS: Microsoft Windows 7 Ultimate x64 [Version 6.1.7601] MySQL Server: Ver 5.5.16 (MySQL Community Server (GPL) Standard XAMPP distribution 1.7.7) In commnad line utility it works (btw, why not?!) mysql> select updated*1 FROM ilance_stores_krabs; +----------------+ | updated*1 | +----------------+ | 20120116161616 | | 20120117154233 | | 20120117113459 | +----------------+ 3 rows in set (0.00 sec) mysql> But in MySQL Workbench query Editor it permanently crashed. Other queries works great except this one.
[25 Jan 2012 21:17]
Rafael Antonio Bedoy Torres
Verified using Workbench 5.2.37 CE Rev. 8576
[27 Mar 2012 1:59]
Philip Olson
Fixed as of 5.2.39, and here's the changelog entry: A query like "SELECT foo+1 FROM bar" could cause a crash.