#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: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:10 David Szotten]:
> do you know off the top of your head what mechanism makes it a no-op on
pg already?
There is nothing specific to PostgreSQL here, it's also a noop on MySQL
and Oracle. It's caused by remaking tables on SQLite that is necessary in
most of cases (see related ticket #32502). Overwriting
`_field_should_be_altered()` in the SQLite backend should do the trick.
--
Ticket URL: <https://code.djangoproject.com/ticket/33471#comment:11>
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.32e21bdab867ff0ff4638f5729836762%40djangoproject.com.
