#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 | Keywords: migrations oracle rename table
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------------
Django Migration's alter_db_table does not rename sequences and triggers.
This causes problems after renaming a table with the Django Migration.
I've written a patch to change the sequences and triggers when an Oracle
table is renamed with alter_db_table.
See pull request:
https://github.com/django/django/pull/4567
--
Ticket URL: <https://code.djangoproject.com/ticket/24715>
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/054.ae5c5afae4e0a8dbd99ac43bb430846e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
