#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-2
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 andrewgodwin):
The rename detector prefers false negatives rather than false positives,
so this is expected behaviour.
However, declining or missing the rename was making django emit a CREATE
then a DELETE for the fields in that order, rather than (correctly) DELETE
then CREATE. I've fixed this, so at least it'll run without errors.
--
Ticket URL: <https://code.djangoproject.com/ticket/23101#comment:11>
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.322898de51f6b8f0b52721e0ad6d4b09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
