#35305: No-op rename of field with `db_column` drops and recreates
constraints/indexes.
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Ahmed
Type: | Ibrahim
Cleanup/optimization | Status: assigned
Component: Migrations | Version: 4.2
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 Jacob Walls):
Thanks, but before getting started I would evaluate if the situation has
already been fixed in the [https://github.com/django/django/pull/18546 PR]
for the closely related #35038. At the very least I would encourage
branching off of that work.
--
Ticket URL: <https://code.djangoproject.com/ticket/35305#comment:6>
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/01070192825bd96d-d66ebb4d-b650-454d-ae22-dd4d4d050d31-000000%40eu-central-1.amazonses.com.
