RenameField with db_column should be a noop.
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)
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
|
Owner: |
changed from nobody to Iuri de Silvio
|
Status: |
new → assigned
|
Cc: |
Simon Charette 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
|
Patch needs improvement: |
set
|
Patch needs improvement: |
unset
|
Patch needs improvement: |
set
|
Patch needs improvement: |
unset
|
Triage Stage: |
Accepted → Ready for checkin
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
I did a pull request here. https://github.com/django/django/pull/13236