#33471: AlterField operation should be noop when adding/changing choices.
--------------------------------------+------------------------------------
Reporter: David Szotten | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by David Szotten):
oh i didn't realise that this was done globally by attr name. (though how
come pg does the right thing?)
could marking `choices` as a `non_database_attrs` adversely impact third
party fields that eg use a pg enum type to model `choices` values?
--
Ticket URL: <https://code.djangoproject.com/ticket/33471#comment:3>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.d4210b6818b1acd993d8f48d32f478bd%40djangoproject.com.
