Bug #9327 Table Editor produces invalid SQL
Submitted: 22 Mar 2005 6:57 Modified: 22 Apr 2005 11:12
Reporter: David Snell Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.2 OS:Microsoft Windows (Windows XP)
Assigned to: CPU Architecture:Any

[22 Mar 2005 6:57] David Snell
Description:
Since I moved my database onto a new server, Query Browser doesn't edit tables properly. (The old server used 4.0.?, the new server uses 4.1.10; I transferred the database using mysqldump and mysql; the charset and collation have always been the default).

Table definition:
CREATE TABLE `tblflags` (
  `RequestID` int(11) default NULL,
  `FlagID` int(11) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

Result of clicking the diamond next to 'RequestID' to make it the primary key:
ALTER TABLE `csdb`.`tblflags` MODIFY COLUMN `RequestID` INTEGER CHARACTER SET NULL COLLATE NULL NOT NULL
, ADD PRIMARY KEY(`RequestID`);

Result of setting the type of 'FlagID' to varchar:
ALTER TABLE `csdb`.`tblflags` MODIFY COLUMN `FlagID` VARCHAR CHARACTER SET NULL COLLATE NULL;

Result of setting charset to 'Default':
ALTER TABLE `csdb`.`tblflags` OLLATE Default;

How to repeat:
As above
[22 Mar 2005 11:12] MySQL Verification Team
I wasn't able to repeat the behavior reported with version 1.1.6.
Please upgrade and try to repeat.
[22 Apr 2005 23:00] Bugs System
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".