Someone faced the problem with double generated unique ids at propel migration?

UK7KBE2JW

Someone faced the problem with double generated unique ids at propel migration?

CREATE TABLE "spy_store" ( "id_store" INTEGER NOT NULL, "name" VARCHAR(255), PRIMARY KEY ("id_store"), CONSTRAINT "spy_store_u_a96012" UNIQUE ("id_store","id_store") );

UK6DVEY91

yes, we´ve updated spryker/propel to fix this.

UK7KBE2JW

I am at the newest version

Unknown

that looks interesting

Unknown

🤔

Unknown

does it make it crash?

UK7KBE2JW

yes

UK7KBE2JW

Propel\Runtime\Exception\RuntimeException - Exception: Failed to execute SQL "CREATE TABLE "spy_store"
(
"id_store" INTEGER NOT NULL,
"name" VARCHAR(255),
PRIMARY KEY ("id_store"),
CONSTRAINT "spy_store_u_a96012" UNIQUE ("id_store","id_store")
)". Aborting migration.

UKHD8KTMF

@UK7KBE2JW What DB are you using?

UK7KBE2JW

postgres, but i got rid of the problem

Unknown

care to share the solution? 🙂

Unknown

or maybe the problem 😄

UK7KBE2JW

there was an old schema file with wrong naming so the merge was messed up