#24563: Migration for M2M Field fails with FieldDoesNotExist when removing
null=True from model
----------------------------+---------------------------------------------
Reporter: GitRon | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords: migrations, many2many, nullable
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+---------------------------------------------
I removed the null=True as suggested in django 1.8 warnings from my M2M
field in the model.
django migrations created the following:
class Migration(migrations.Migration):
[...]
operations = [
migrations.AlterField(model_name='project', name='my_field',
field=models.ManyToManyField(related_name='in_charge_projects',
verbose_name='label', to='account.Employee', blank=True),
),
[...]
]
I get the following error:
"django.core.exceptions.FieldDoesNotExist: Project_my_field has no field
named None"
--
Ticket URL: <https://code.djangoproject.com/ticket/24563>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.79973c275ddea36d7f2dfb005ae55eac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
