MySQL Bugs: #22418: first created column INTEGER, UNSIGNED, NOT NULL and PRIMARY KEY

Bug #22418	first created column INTEGER, UNSIGNED, NOT NULL and PRIMARY KEY
Submitted:	16 Sep 2006 20:40	Modified:	14 Jan 2009 16:54
Reporter:	Cezary Okupski	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Administrator	Severity:	S4 (Feature request)
Version:	1.2.3 rc	OS:	MacOS (Mac OS X)
Assigned to:		CPU Architecture:	Any
Tags:	column, create, first, id, INTEGER, NOT NULL, primary key, table, UNSIGNED

Description:
It would be great if creating new columns in table editor behaved the same way on Mac OS X as on Windows - if first created column was INTEGER, UNSIGNED, NOT NULL and PRIMARY KEY. Next columns appropriately.

I was astonished when MySQL Administrator predicted my intentions for the first time. No other popular MySQL tools do so! Just please port this feature to Mac OS X.

I guess it is a matter of versions for each operating system, because both in Mac OS and in Windows I create tables on MySQL 5 servers.

How to repeat:
Add a column to a newly created table on Windows.
Add a column to a newly created table on Mac OS.
Compare.

Suggested fix:
Port Windows solution to Mac OS Administrator's version

Many thanks for writing a feature request. We are on the way to implement full functionality of Administrator into Workbench and won't implement your idea anymore.