A table column with .autoIncrement() and NO .primaryKey() does create primary key with SchemaUtils.createMissingTablesAndColumns()

[sobvan]

Given the following code:

object NoPrimaryKey: Table() {
    val autoIncrementValue: Column<Long> = long("auto_increment_value").autoIncrement()
    val someOtherValue: Column<String> = varchar("some_other_value", 20)
}

object StringPrimaryKey: Table() {
    val autoIncrementValue: Column<Long> = long("auto_increment_value").autoIncrement()
    val someOtherValue: Column<String> = varchar("some_other_value", 20).primaryKey()
}

fun main() {
    val db = Database.connect(
            "jdbc:postgresql://localhost:5432/postgres",
            "org.postgresql.Driver",
            "postgres",
            "lUosBQd2Sq")
    transaction(db) {
        SchemaUtils.createMissingTablesAndColumns(NoPrimaryKey, StringPrimaryKey)
    }
}

produces the following CREATE TABLE sql statements:

CREATE TABLE IF NOT EXISTS noprimarykey (auto_increment_value BIGSERIAL NOT NULL, some_other_value VARCHAR(20) NOT NULL, CONSTRAINT pk_NoPrimaryKey PRIMARY KEY (auto_increment_value))
CREATE TABLE IF NOT EXISTS stringprimarykey (auto_increment_value BIGSERIAL NOT NULL, some_other_value VARCHAR(20) PRIMARY KEY)

I do not get why the table noprimarykey will be created with the PRIMARY KEY constraint.

Is there an explanation, or is this a bug?

[sobvan]

Thanks a lot for fixing this.

[Tapac]

@istvanszoboszlai , hope to release it soon (on the next week)