#33953: RenameModel breaking change in 4.1 with ManyToManyField
-------------------------------------+-------------------------------------
Reporter: Timothy Thomas | Owner: Iuri de
| Silvio
Type: Bug | Status: assigned
Component: Migrations | Version: 4.1
Severity: Release blocker | Resolution:
Keywords: RenameModel | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Iuri de Silvio):
* owner: nobody => Iuri de Silvio
* status: new => assigned
Comment:
I would expect the field name using the `db_table` to generate their name
instead of the model name, but I agree it should not change the existing
behavior.
Looks like an easy fix, I'll write a test and try it today.
--
Ticket URL: <https://code.djangoproject.com/ticket/33953#comment:3>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070182cfb1f52b-5018fedd-f2db-4a2f-843b-b19c8092f575-000000%40eu-central-1.amazonses.com.
