#23630: AlterModelTable doesn't rename auto-created tables
---------------------------------+-------------------------------------
Reporter: Naddiseo | Owner: timgraham
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Comment (by andrewgodwin):
tim: During autodetection, the relations occasionally don't have
rel.through populated and I'm not sure why that's the case. There's a
couple of checks elsewhere for this same behaviour, but I think before it
was just ForeignKeys having an unused through or something (it's been long
enough that I can't remember).
Technically, the rename should be done by AlterModelTable rather than by
the autogenerator making extra stanzas of changes (in the same way that
RenameField also modifies FKs that point to it), but I don't mind this
solution either if it works well.
--
Ticket URL: <https://code.djangoproject.com/ticket/23630#comment:8>
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/066.85fb9bffeb3c7e3856efc8b686a0d5b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
