Currently making column as UNIQUE does not have any effect on DDL. Patch makes it work with PostgreSQL. Please check it better as I'm not SQL wizard and may have missed something obvious.
I don't about other database systems, but in PostgreSQL at lest, all PRIMARY keys are implicitly UNIQUE so there's no need to add UNIQUE constrain for columns that are alone PRIMARY KEY.
If so, there should be instead and also "Table information dialog" UNIQUE check box could be grayed for columns that alone PRIMARY KEY.
if (!normalColumn.isPrimaryKey() && normalColumn.isUniqueKey()) {
ddl.append(" UNIQUE");
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't about other database systems, but in PostgreSQL at lest, all PRIMARY keys are implicitly UNIQUE so there's no need to add UNIQUE constrain for columns that are alone PRIMARY KEY.
If so, there should be instead and also "Table information dialog" UNIQUE check box could be grayed for columns that alone PRIMARY KEY.
if (!normalColumn.isPrimaryKey() && normalColumn.isUniqueKey()) {
ddl.append(" UNIQUE");
Thank you for your patch.
It is referenced at version 1.0.0.v20091221-1350
about he relation between UNIQUE check box and alone PRIMARY KEY,
I will consider.