#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 jwineinger):
I admit that wasn't the use case I was trying to fix. It seems that there
are multiple situation where migrations create states with zero columns in
a table. I don't see the relevance in what you describe to the problem I
was having, so perhaps they are separate symptoms of this same problem.
When you say "it is not about a DeleteModel operation following a
RemoveField. That could just remove that field", what do you mean?
Should the approach be to change the auto-detector to not produce states
with zero columns, or should we try and handle that somewhere else?
--
Ticket URL: <https://code.djangoproject.com/ticket/24424#comment:21>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.c693cd3736fd008ae5aaa0ead88c9b61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
