castorp wrote:That the primary key is enforeced through a constraint is a technical detail. A DBMS is free on how it enforeces that, it does not need to use a constraint for that.
It would be best to clarify what "primary key" is referring to in the UI. As you point out, we can't assume that this is the name of a constraint.
The lack of datatype may be interpreted as an effort to provide a shortcut that ensures the presence of a primary key, but not a replacement for the column-properties UI.
I haven't encountered this ambiguity with other DB-design tools (Data ERWin, ERStudio, SQL Editor).
No, moving the non-key column to the top doesn't make it disappear. It simply moves above the tiny blank row in the diagram. So the drawing problem appears to be specific to key columns.