#31826: AlterField with only db_column changed should be a noop
------------------------------------------------+------------------------
Reporter: Iuri de Silvio | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 3.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
When I change: `pink = models.Integer(default=0)` to `pink =
models.Integer(default=0, db_column="pink")` the migration can recreate
constraints if it is an FK or even reconstruct the table (SQLite).
The (same) constraint drop/create is a blocking operation for PostgreSQL,
so it is an undesirable and unexpected behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/31826>
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/053.5aebd96142fdc453bad754329bfdf11d%40djangoproject.com.
