#35305: No-op rename of field with `db_column` drops and recreates
constraints/indexes.
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"b2407e4d7d25e4a5839bb512cb2fdf71e9e30a21" b2407e4]:
{{{#!CommitTicketReference repository=""
revision="b2407e4d7d25e4a5839bb512cb2fdf71e9e30a21"
Fixed #35305 -- Avoided recreating constraints on fields renamed via
db_column.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35305#comment:10>
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 visit
https://groups.google.com/d/msgid/django-updates/010701979cae9e58-c06b961d-afed-463c-a278-8f39f65147cb-000000%40eu-central-1.amazonses.com.
