Bug #14269 Adding/altering INT value to UNSIGNED ZEROFILL causes crash
Submitted: 24 Oct 2005 17:59 Modified: 3 Dec 2005 4:45
Reporter: Gary Whitmore Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.1.0 OS:MacOS (Mac OS X 10.4.2 (Tiger))
Assigned to: CPU Architecture:Any

[24 Oct 2005 17:59] Gary Whitmore
Description:
While creating or editing a table in MySQL Administrator, adding a column of type INT(num) with flags UNSIGNED ZEROFILL causes the program to crash, or results in the program freezing.

MySQL Query Browser can read and write INT(num) UNSIGNED ZEROFILL columns, and MySQL Administrator can still work with INT(num) UNSIGNED ZEROFILL as long as it already exists (e.g. you can set a default value).

How to repeat:
1. Create a new table.
2. Add a column with type INT(num), where "num" is any reasonable number for type INT.
3. Select UNSIGNED and ZEROFILL under the "Flags".
4. Hit "Apply".

Suggested fix:
The only workaround I can find is to use the command-line interface for MySQL to add the column.
[25 Oct 2005 11:56] Valeriy Kravchuk
Thank you for a problem report. I was not able to repeat it with Administrator version 1.1.3 on Windows and InnoDB table, though. The generated (using the steps you described) statement:

ALTER TABLE `test`.`test_1` ADD COLUMN `c1` INTEGER(11) UNSIGNED ZEROFILL NOT NULL AFTER `name`;

was executed without any problems.

Please, try to use newer version of MySQL Administrator. Do you work with MyISAM table? What version of MySQL server is used?
[26 Oct 2005 18:17] Gary Whitmore
Sorry. I downloaded the pre-built binary for Tiger a few weeks ago; I'll probably have to wait for the latest binary release (since I'm not the one who can install the necessary packages). But for the information you wanted, it's a MyISAM database with dynamic rows.
[26 Oct 2005 21:30] Jorge del Conde
Thanks for your bug report.  I was able to reporduce this in OSX 10.4
[3 Dec 2005 4:45] Alfredo Kojima
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html