-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Altering Unique, nullable field to Non-nullable #22
Comments
Thanks for this report, we will review the issue and existing PR from ESSolutions/django-mssql-backend#77. |
Hello, any plan any time soon for the existing PR ? I am also running into the same error within the same context:
|
I have the same issue, following.. |
This issue should be fixed by PR #163. I am going to close this issue but if you are still having the same issue feel free to reopen this issue. |
This has been an on-going issue with the Django MSSQL backend. I've experienced it on more than one occasion in my own code and third party modules, the most recent occurring when attempting to integrating djangorestframework-api-key into an existing project.
Running migrations on the newly installed module results in the following failure:
On closer inspection one of the migrations is altering a field from unique=True, null=True to a unique nullable field. Typically, if I run into this issue in my own code, I'll just work around it and make the necessary changes. In this case, I'm concerned about future compatibility issues with the djangorestframework-api-key down the road if I make those changes myself.
Some additional info from the forked project can be found here: ESSolutions/django-mssql-backend#77
The text was updated successfully, but these errors were encountered: