fix(migration): Avoid unique constraint violation

Created by: Tirokk

Authored by roschaefer Mar 20, 2020 Merged Mar 23, 2020

---

Pullrequest

Apparently we have posts or users which have the same imageUrl or avatar. If we create image nodes we will run into unique constraint violations when we try to create the unique index.

When I try to yarn run db:migrate up on production data on my machine and in docker the migration takes way too much time. If you create the unique index first, it's doing fine.

Issues

• None

Todo

• Check migration with image files (locally or on staging)