Bug #7039 Wrong ALTER TABLE statement if you try to set column as auto_increment
Submitted: 6 Dec 2004 13:53 Modified: 7 Dec 2004 21:03
Reporter: Victoria Reznichenko Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.2 OS:Windows (Windows)
Assigned to: CPU Architecture:Any

[6 Dec 2004 13:53] Victoria Reznichenko
Description:
If I try to set column as auto_increment, QB generates the following ALTER TABLE statement:

ALTER TABLE `test`.`a` MODIFY COLUMN `id` INTEGER CHARACTER SET NULL COLLATE NULL NOT NULL DEFAULT 0 AUTO_INCREMENT;

How to repeat:
1. Create table:

CREATE TABLE `a` (`id` int(11) NOT NULL default '0',
`str` char(1),
PRIMARY KEY  (`id`))
ENGINE=InnoDB DEFAULT CHARSET=latin1;

2. Set column 'id' as auto_increment and press 'Apply changes'
[7 Dec 2004 21:03] Michael G. Zinner
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