#24424: Removing a model's last field results in SQL syntax error on SQLite
----------------------------+------------------------------------
Reporter: adnam | Owner: adnam
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Changes (by MarkusH):
* keywords: sqlite3 migrations =>
* component: Database layer (models, ORM) => Migrations
* needs_tests: 0 => 1
Comment:
Ok, the failing test on MySQL shows its non-standard behavior again. And
also shows that the fundamental problem is not just the SQLite backend,
but also the autodetector that generates models without any fields. This
is not a valid model and thus shouldn't be generated by the migrations
(and hence the migration autodetector).
I don't have a patch for that ready, but I can verify the problem. Fixing
only the SQLite schema editor won't do it.
--
Ticket URL: <https://code.djangoproject.com/ticket/24424#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 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.5b1e8190107b9aa7be39518a48c46b8d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
