Bug #67184 Table creation with same name, different datatype
Submitted: 11 Oct 2012 3:11 Modified: 16 Oct 2012 0:28
Reporter: Bill Frost Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.43 OS:Microsoft Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[11 Oct 2012 3:11] Bill Frost
Attempt to create a table with (inadvertently) the same column name and a different datatype

----- Developer Notes -----

MySQL Workbench CE for Windows version 5.2.43  revision 9869
Configuration Directory: C:\Users\Bill\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
CPU: 2x Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz, 3.3 GiB RAM
Active video adapter (0): ATI Mobility Radeon X1400
Installed video RAM: 128 MB
Current video mode: 1920 x 1200 x 4294967296 colors
Used bit depth: 32
Driver version: 8.561.0.0
Installed display drivers: atiumdag,atiumdva,atiumd64.dll,atiumd6a.cap,atitmm64.dll
Current user language: English (Australia)

Exception = System.NullReferenceException
Message = Object reference not set to an instance of an object.
FullText = System.NullReferenceException: Object reference not set to an instance of an object.
   at MySQL.Utilities.AdvNodeTextBox.textBox_TextChanged(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnTextChanged(EventArgs e)
   at System.Windows.Forms.TextBoxBase.OnTextChanged(EventArgs e)
   at System.Windows.Forms.TextBoxBase.WmReflectCommand(Message& m)
   at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
   at System.Windows.Forms.TextBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

How to repeat:
Note that this was really my mistake!  I created a new table.  I created a column minLongitude with datatype DOUBLE.  I then mistakenly created a column of the same name and if defaulted to varchar(45).  When I pressed Tab, it crashed.
[11 Oct 2012 16:01] Miguel Solorzano
Please check if the same issue happens with version 5.2.44. Thanks.
[11 Oct 2012 21:04] Bill Frost
Miguel, I just tried to reproduce this in 5.2.44 and it behaved correctly.  I deliberately created two identical column names with different datatypes plus a few other columns.  When I went to Apply the changes, I was quite correctly advised of a syntax error.

Thanks, Bill
[16 Oct 2012 0:28] Miguel Solorzano
Thank you for the feedback.