#23101: Changing name of M2MField while db_table keeps table name unchanged
leads
to spurious migration that changes table name
-------------------------------------+-------------------------------------
Reporter: maney@… | Owner:
Type: Bug | abraham.martin
Component: Migrations | Status: closed
Severity: Release blocker | Version: 1.7-rc-1
Keywords: | Resolution: fixed
Has patch: 0 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andrew Godwin <andrew@…>):
In [changeset:"e1347e9253821a31f9896de9eb993e2376e7398f"]:
{{{
#!CommitTicketReference repository=""
revision="e1347e9253821a31f9896de9eb993e2376e7398f"
Fixed #23101 db_table wasn't copied in deconstruct
Forward port of 999758fc7a2d6fcb01eb40de937d4420f884788d from
stable/1.7.x
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23101#comment:5>
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/073.0544f19df15329206731999a4d4584d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
