[Django] #24715: Django Migration's alter_db_table does not rename sequences and triggers.
Django
-----------------------------+--------------------------------------------
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.
Django
Reporter: johnrtipton | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
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
Changes (by johnrtipton):
* needs_better_patch: => 0
* has_patch: 0 => 1
* needs_tests: => 1
* needs_docs: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/24715#comment:1>
Django
Reporter: johnrtipton | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Keywords: migrations oracle | Triage Stage:
rename table | Unreviewed
Has patch: 1 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Comment (by timgraham):
What problems does it cause? (Trying to determine if the fix should be
backported to 1.7 and/or 1.8).
--
Ticket URL: <https://code.djangoproject.com/ticket/24715#comment:2>
Django
Reporter: johnrtipton | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Keywords: migrations oracle | Triage Stage:
rename table | Unreviewed
Has patch: 1 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by shaib):
* cc: shaib (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/24715#comment:3>
Django
Reporter: johnrtipton | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Keywords: migrations oracle | Triage Stage:
rename table | Unreviewed
Has patch: 1 | Needs documentation: 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
Reporter: johnrtipton | Owner: nobody
Type: Bug | Status: new
Severity: Release blocker | Resolution:
Keywords: migrations oracle | Triage Stage: Accepted
rename table |
Has patch: 1 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timgraham):
* version: master => 1.7
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Very well, we are just awaiting tests and a mention in the 1.8.1 and 1.7.8
release notes then.
--
Ticket URL: <https://code.djangoproject.com/ticket/24715#comment:5>
Django
-------------------------------------+-------------------------------------
Reporter: johnrtipton | Owner: nobody
Type: Bug | Status: new
Severity: Release blocker | Resolution:
Keywords: migrations oracle | Triage Stage: Accepted
rename table |
Has patch: 1 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
--
Ticket URL: <https://code.djangoproject.com/ticket/24715#comment:6>
Django
-------------------------------------+-------------------------------------
Type: Bug | Status: new
Severity: Normal | Resolution:
Keywords: migrations oracle | Triage Stage: Accepted
rename table |
Has patch: 1 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by timgraham):
* severity: Release blocker => Normal
Comment:
While this issue remains a candidate for backport, I suppose we should
demote it from "release blocker" as it's not blocking any releases.
--
Ticket URL: <https://code.djangoproject.com/ticket/24715#comment:7>
Django
-------------------------------------+-------------------------------------
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: duplicate
Keywords: migrations oracle | Triage Stage: Accepted
rename table |
Has patch: 1 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
Changes (by charettes):
* status: new => closed
* resolution: => duplicate
Comment:
It's the same underlying issue as #23577.
--
Ticket URL: <https://code.djangoproject.com/ticket/24715#comment:8>