Re: [Django] #35305: No-op rename of field with `db_column` drops and recreates constraints/indexes. (was: No-op rename of field with `db_column` drops and recreates constraints)

8 views
Skip to first unread message

Django

unread,
Mar 17, 2024, 4:38:31 AM3/17/24
to django-...@googlegroups.com
#35305: No-op rename of field with `db_column` drops and recreates
constraints/indexes.
--------------------------------------+------------------------------------
Reporter: Jacob Walls | Owner: nobody
Type: Cleanup/optimization | Status: new
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
--------------------------------------+------------------------------------
Changes (by Mariusz Felisiak):

* stage: Unreviewed => Accepted
* summary: No-op rename of field with `db_column` drops and recreates
constraints =>
No-op rename of field with `db_column` drops and recreates
constraints/indexes.

Comment:

Tentatively accepted.
--
Ticket URL: <https://code.djangoproject.com/ticket/35305#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Reply all
Reply to author
Forward
0 new messages