Bug #33674 Lowercased word "UNSIGNED" in column definitions is skipped when importing SQL
Submitted: 3 Jan 2008 19:30 Modified: 4 Jan 2008 12:07
Reporter: Martin Mayer Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.11 OSS Beta Rev 2360 OS:Windows (XP Pro)
Assigned to: Sergei Tkachenko CPU Architecture:Any
Tags: sql import

[3 Jan 2008 19:30] Martin Mayer 
Description:
When importing SQL script into MWB, word "UNSIGNED" in column definitions must be written upper-cased. If written lower-cased, column is not flagged as unsigned.

How to repeat:
Import (Menu File/Import/Reverse Engineer MySQL Create Script...) uploaded file containing this table:

CREATE TABLE `testtab` (
  `col1` int(10) UNSIGNED NOT NULL,
  `col2` int(10) unsigned NOT NULL
);

"col1" with upper-cased "unsigned" is correctly imported as unsigned int but "col2" with lower-cased "unsigned" as signed int.
[3 Jan 2008 19:33] Martin Mayer 
Create table testtab

Attachment: import.sql (application/octet-stream, text), 103 bytes.
[3 Jan 2008 20:27] MySQL Verification Team 
Thank you for the bug report.
[4 Jan 2008 12:07] Sergei Tkachenko 
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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html