Fixed failing migrations caused by foreign key constraints
Motivation
I was comparing v5.0.0 and v5.1.0 in v5.0.0...v5.1.0#migrations.go and saw that one key difference is that I in #144 removed the double-migration, first without foreign key constraints, and then again with them.
It turns out our foreign key constraints has some circular dependencies. Fixing the database relations is postponed into #146. This PR is a band-aid fix.
I've now properly tested this in docker-compose using Postgres, as I should've done before.
CHANGELOG.mdfile, according to docs: https://iver-wharf.github.io/#/development/changelogs/writing-changelogsSummary
Motivation
I was comparing v5.0.0 and v5.1.0 in v5.0.0...v5.1.0#migrations.go and saw that one key difference is that I in #144 removed the double-migration, first without foreign key constraints, and then again with them.
It turns out our foreign key constraints has some circular dependencies. Fixing the database relations is postponed into #146. This PR is a band-aid fix.
I've now properly tested this in docker-compose using Postgres, as I should've done before.
Closes #160