Bug #102452 FR Change default behaviour for PK creation
Submitted: 2 Feb 2021 15:50 Modified: 6 Feb 2022 10:40
Reporter: John King Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S4 (Feature request)
Version:8.0.23, 8.0.28 OS:Any (Microsoft Windows 10 Pro)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[2 Feb 2021 15:50] John King 
Description:
In the designer the default first column is a primary key. The first field is create automatically, withou user intervention, with PK (primary key index) and NN (NOT NULL) attributes. In addition the configuration allows to change the default column name pattern and the default type (INT). 

It would be helpful to also allow the default to
1) Allow creation of INSIGNED INT or make this the default (just like PK and NN)
2) Create the column as AUTO_INCREMENT (Just like PK and NN)

How to repeat:
Rationale
These could be a fixed default (just like the key creation) or an optional value. But I can see no detrimental effects of creating the PK as UNISIGNED rather as SIGNED value. Typically the PK of a table is auto increment. The combination of default AI and UNSIGNEDness allows for the widest key space.
[6 Feb 2022 10:19] MySQL Verification Team 
Hello John,

Thank you for the report and feedback.

regards,
Ashwini
[6 Feb 2022 10:40] John King 
Typo : UNSIGNED INT NOT NULL AUTOINCREMENT would be the optimal definiton.