#24424: Removing a model's last field results in SQL syntax error on SQLite
----------------------------+------------------------------------
Reporter: adnam | Owner:
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by adnam):
I notice this bug is still open after 4 months. My feeling is that
reproducing it by creating a rather convoluted series of migrations is
rather the wrong way to go about it. The error is quite simple as I
[[https://github.com/django/django/pull/4325#issuecomment-85060638|explained
earlier]], and the fix is just a
[[https://github.com/django/django/pull/4325/files#diff-
0c8f495bfee773ab7b5409533bd6d7efL142|2-line change in
db/backends/sqlite3/schema.py]]. The bug only affects the sqlite schema
editor as it uniquely deletes then re-creates tables upon migrations.
Reproducing the error via migrations is rather like eating sushi with 10m-
long chopsticks, since the bug is several layers down the internal API.
Just my tuppence worth.
--
Ticket URL: <https://code.djangoproject.com/ticket/24424#comment:25>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.8874ac8320ff40333e72c2f656db0f4c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
