Opened 4 years ago
Last modified 4 years ago
#31825 closed Cleanup/optimization
RenameField with db_column defined drop and recreate the same constrainsts on Postgres — at Version 1
| Reported by: | Iuri de Silvio | Owned by: | nobody |
|---|---|---|---|
| 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 |
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 (1)
comment:1 by , 4 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 |
Note:
See TracTickets
for help on using tickets.