Open Lorac opened 1 week ago
Thats right. You should delete the duplicate row manually before revert.
Would it be possible to squash all the migrations together?
It's not recommended because of this public library is being used across multiple servers in different situations. There are on other status and we want to allow them to move to a new version of the library without any issues.
After I imported the data, I wanted to restart fresh, so I tried to migrate backward.
Since I wanted to restart fresh, I deleted the offending cities. But I got more from the slug, too:
Since there is duplication, It is impossible to revert to the old unique_together key which is :
'unique_together': set([('region', 'name'), ('region', 'slug')]),