#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
--------------------------------------+------------------------------------
Comment (by Shubham Singh Sugara):
Replying to [comment:2 Giannis Terzopoulos]:
> I had a brief look at this and it seems related to #35038 and the
suggestion to add a new
[https://github.com/django/django/pull/17846#issuecomment-1949371939
AlterConstraint operation]. So maybe it's best to have that operation in
place before someone works on this ticket.
I commented on #35308 to see if issue is still there or some one is
working on it
Maybe i can give it a try if no one else is trying , the old PR was closed
due to solution not being right ,so lets see
--
Ticket URL: <https://code.djangoproject.com/ticket/35305#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701917a86c45c-695707b6-e213-4e6f-8352-d18d71a4413f-000000%40eu-central-1.amazonses.com.
