-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
Auto-generated migration after clean install (Django 2.1) #267
Comments
But what is the actual change in this migration?
|
The limit_choices_to={'subscribed': True} appears to be new, just as the db_index. At least, when I compare with the initial migration. |
This is weird. I'd really like to be sure whether this is is a Django 2.1 thing or whether this pertains to a specific change on our side. And if so, which change. In the latter case, I will happily merge a PR with reference to this particular change. |
Also happening here, I recently migrated from django 1.11 to django 2.0 and it creates a new migration for newsletter. |
Happened again.
|
On commit 30c3ec3 when I run makemigrations I get a new migration (0005). This is on Django 2.1, but I don't think that will affect it.
Alter field subscriptions on submission
Maybe this migration should be added to the package, as I don't like having 'self-generated' migrations inside a package.
The text was updated successfully, but these errors were encountered: