#23577: Rename operations should rename indexes, constraints, sequences and
triggers named after their former value
---------------------------------+------------------------------------
Reporter: Chris Woytowitz | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | 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 Steven Mapes):
So I ended up created a duplicate of this ticket for issue #34647 but
thanks to clavay's suggestion I managed to also get a work around by
running {{{makemigrations}}}then editing the {{{CreateModel}}} and
changing the name and db_table entries for all tables that were created (I
use custom table names as the app name prefix breaks the DB naming
convention policy that's in place for the project.
I then added {{{migrations.RenameModel}}} statements for each of the
models I needed to rename back, four of them, then finally had to run a
{{{migrations.RunSQL}}} to perform the actual rename of the underlying
databases tables.
--
Ticket URL: <https://code.djangoproject.com/ticket/23577#comment:36>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070188aede1139-59f08f5a-69f5-41ac-8589-421504103e98-000000%40eu-central-1.amazonses.com.
