#33471: AlterField operation should be noop when adding/changing choices on
SQLite.
-------------------------------------+-------------------------------------
Reporter: David Szotten | Owner: Douglas
Type: | Mumme
Cleanup/optimization | Status: assigned
Component: Migrations | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Johnson):
Indeed it would break Django-MySQL’s `EnumField` - [https://django-
mysql.readthedocs.io/en/latest/model_fields/enum_field.html docs] /
[https://github.com/adamchainz/django-
mysql/blob/main/src/django_mysql/models/fields/enum.py source].
If the "ignorable attrs" were extended on a per-field-class basis, that
could work. It would be a bigger patch but it could allow many custom
field classes to avoid unnecessary database changes.
--
Ticket URL: <https://code.djangoproject.com/ticket/33471#comment:8>
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/070.3d1d3ed3da7f18f0b89ef83fafdc447b%40djangoproject.com.
