#33471: sqlite no-op migrations
-----------------------------------------+------------------------
Reporter: David Szotten | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 4.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 |
-----------------------------------------+------------------------
while writing a test case for #33470 i found that for sqlite, even a
seemingly db-transparent change like adding `choices` still generates sql
(new table + insert + drop + rename) even though this shouldn't be needed.
on e.g. postgres the same migration generates no sql
--
Ticket URL: <https://code.djangoproject.com/ticket/33471>
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/055.136a238cdf36a5345f6ff1fd36aef11e%40djangoproject.com.
