Opened 5 years ago
Closed 5 years ago
#31825 closed Cleanup/optimization (fixed)
RenameField with db_column should be a noop.
Reported by: | Iuri de Silvio | Owned by: | Iuri de Silvio |
---|---|---|---|
Component: | Migrations | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Simon Charette | Triage Stage: | Ready for checkin |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | |||
Description (last modified by ) ¶
RenameField with db_column should be a noop because it is only the Django column that changed, the database still have the same db_column.
Change History (11)
comment:1 by , 5 years ago
Description: | modified (diff) |
---|---|
Summary: | RenameField with db_column defined drop and recreate the same constrainsts → RenameField with db_column defined drop and recreate the same constrainsts on Postgres |
comment:2 by , 5 years ago
comment:3 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 5 years ago
Version: | 3.0 → master |
---|
comment:5 by , 5 years ago
Cc: | added |
---|---|
Has patch: | set |
Summary: | RenameField with db_column defined drop and recreate the same constrainsts on Postgres → RenameField with db_column should be a noop. |
Triage Stage: | Unreviewed → Accepted |
Thanks. See related ticket when Simon pointed out that such change (3 & 4) should be a noop.
Version 0, edited 5 years ago by (next)
comment:6 by , 5 years ago
Patch needs improvement: | set |
---|
comment:7 by , 5 years ago
Patch needs improvement: | unset |
---|
comment:8 by , 5 years ago
Patch needs improvement: | set |
---|
comment:9 by , 5 years ago
Patch needs improvement: | unset |
---|
comment:10 by , 5 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
Note:
See TracTickets
for help on using tickets.
I did a pull request here. https://github.com/django/django/pull/13236