#24715: Django Migration's alter_db_table does not rename sequences and
triggers.
-------------------------------------+-------------------------------------
Reporter: johnrtipton | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: migrations oracle | Triage Stage:
rename table | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by johnrtipton):
Yes, it should be backported to 1.7 and added to 1.8. I've backported it
into my 1.7.7 branch.
When you use migrations.RenameModel in a migration, it does not rename
sequences or triggers. This prevents the tables autonumber from working
and causes orphaned triggers and sequences.
--
Ticket URL: <https://code.djangoproject.com/ticket/24715#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.adab13ffcfb5273d8e558e235c30f746%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
