Bug #37220 Edit table crashes on change field name
Submitted: 5 Jun 2008 8:15 Modified: 24 Feb 2009 10:32
Reporter: David Karlin Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.2.12 OS:MacOS (Mac Pro,10.5.3)
Assigned to: CPU Architecture:Any

[5 Jun 2008 8:15] David Karlin
Description:
I have a table (created from a "create select") with a row erroneously labelled min(timestamp). If I try to edit it to change the row name to "timestamp", Query Browser crashes.

Only workaround on Query Browser is to delete the table and start again.

This is only one of a large number of crashes I have on Mac OS X - it's one of the more repeatable ones.

How to repeat:
Here is the SQL for the table create statement:

 CREATE TABLE  `sitestats`.`entries` (
  `hostname` varchar(128) character set utf8 default NULL,
  `min(timestamp)` int(10) unsigned default NULL,
  `url` varchar(255) character set utf8 default NULL,
  `path` varchar(255) character set utf8 default NULL,
  `hosttype` int(11) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1

Create this, then edit the table, change min(timestamp) to timestamp, hit Apply
[5 Jun 2008 17:43] Sveta Smirnova
Thank you for the report.

I can not repeat described behavior. Please indicate which version of MySQL server do you use and SQL_MODE value.
[5 Jun 2008 22:12] David Karlin
The version of MySQL is as follows:

mysql  Ver 14.12 Distrib 5.0.51a, for apple-darwin9.0.0b5 (i686) using readline 5.0

(This is the default as supplied by Apple with the Mac Pro - I haven't modified any of the settings).

SQL_MODE is not set to anything - at least, I'm not aware of having set it, and doing a "SHOW VARIABLES" gives a blank space opposite the sql_mode variable name.
[6 Jun 2008 11:43] Sveta Smirnova
Thank you for the feedback.

I still can not repeat described behavior.

Please connect to mysqld using mysql command line client, then issue query

ALTER TABLE `test`.`entries` CHANGE COLUMN `min(timestamp)` `timestamp` INTEGER UNSIGNED DEFAULT NULL;

And provide us output you get.
[6 Jun 2008 14:46] David Karlin
Sveta,

The command works just fine from the MySQL command line - the table is altered appropriately.

By the way, I do not think the Query Browser ever gets as far as issuing the command to the database: it crashes before it has got round to displaying its usual confirmation screen with "here is a script, do you want to execute this".

Regards

David
[6 Jun 2008 18:00] Sveta Smirnova
Thank you for the feedback.

I still can not repeat described behavior on MacBook Intel with Mac OSX 10.4 installed. Which version of Mac OSX do you run?
[6 Jun 2008 21:12] David Karlin
Hi Sveta,

I'm on OS X version 10.5.3, running on a Mac Pro, which is an Intel 2x2.8 GHz Quad-core Xeon (the current Macbook is an Intel Core 2 Duo). 

As I mentioned, Query Browser is *very* unstable on this (this bug just happens to be very repeatable, unlike most of my other crashes). This could well be the hardware platform. We don't have a Macbook here, but we do have a Mac Mini (which is also a Core 2 Duo) - if it would help, I could try running the program on that  to see if it's more stable.

Thanks
[16 Jun 2008 17:47] Dean Ellis
Verified with Leopard (10.5.3) and Macbook Pro, using steps as described.

Thank you for the report.
[24 Feb 2009 10:32] Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Query Browser into MySQL Workbench. Unfortunately you are using an unsupported platform. More informations about supported platforms you will find here:

http://www.mysql.com/support/supportedplatforms/tools.html

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/