Open gabn88 opened 5 years ago
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.
# Generated by Django 2.2.7 on 2019-11-22 21:11
from django.db import migrations, models
class Migration(migrations.Migration):
dependencies = [
('newsletter', '0004_auto_20180407_1043'),
]
operations = [
migrations.AlterField(
model_name='submission',
name='subscriptions',
field=models.ManyToManyField(blank=True, db_index=True, help_text='If you select none, the system will automatically find the subscribers for you.', limit_choices_to={'subscribed': True}, to='newsletter.Subscription', verbose_name='recipients'),
),
]
On commit 30c3ec3f3bea93b22c6640aed40ee2c8040a4f46 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.