Closed ahukkanen closed 2 years ago
Confirmed it locally.
This problem did not exist in the core in the same migration. This is likely something that was added specifically for MetaDecidim.
Yes, that's odd. I double-checked just to be sure:
This was introduced here at 1bd634f44d0649ee4d87f89ae8a4c65c9790d729. It's probably a problem that only happens/happened in Decidim's first installations (Metadecidim and Barcelona).
It probably needs to be fixed at Barcelona too (cc/ @agustibr): https://github.com/AjuntamentdeBarcelona/decidim-barcelona/blob/master/db/migrate/20170616083641_add_uniqueness_to_name_and_document_number_to_user_groups.decidim.rb
This old migration was referring to a Decidim model which did not understand it had new columns.
Fixing this the same way as we today with other migrations in the core.
This problem did not exist in the core in the same migration. This is likely something that was added specifically for MetaDecidim.
In order to replicate the issue:
bundle exec rails db:drop db:create
bundle exec rails db:migrate