#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: new
Severity: Release blocker | Version: 1.7-rc-2
Keywords: | Resolution:
Has patch: 0 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by maney@…):
* status: closed => new
* version: 1.7-rc-1 => 1.7-rc-2
* resolution: fixed =>
Comment:
The changes in RC2 fix the initial creation, but do little or nothing for
the second migration - that still such a mess that I'm not even sure how
many ways it fails, though I believe the error reported is the same as
ever:
OperationalError: table "x_three_ring" already exists
This is the migration from model-0001 (the initial state) to model-0002
--
Ticket URL: <https://code.djangoproject.com/ticket/23101#comment:6>
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.8b10d9dcd2e44b1572c63b23517626cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
