Opened 22 months ago

Last modified 21 months 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 Iuri de Silvio)

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 Changed 22 months ago by Iuri de Silvio

Description: modified (diff)
Summary: RenameField with db_column defined drop and recreate the same constrainstsRenameField with db_column defined drop and recreate the same constrainsts on Postgres
Note: See TracTickets for help on using tickets.
Back to Top