Unique Index is not dropped

[rjschave]

When a field is changed from nullable to non-nullable, a unique index is created by the migration. Rolling the migration back fails because the unique index is not removed. The field cannot be changed because the unique index still depends on the field.

I encountered this issue with the Wagtail project. I created a project to document steps to reproduce the issue - https://github.com/eclipseconsulting/wagtail-mssql-django-unique-index

This issue seems similar, but not identical to issues #100 and #104.

[absci]

Thanks for the reproduce repo, I'm able to follow the steps and got the same error. We'll investigate this issue and propose a fix.

[jmah8]

This is fixed by PR #93 and will be in the next release.

[jmah8]

I am going to close this issue since it seems to be fixed but feel free to reopen it if there are still issues.