#29182: SQLite 3.26 breaks database migration ForeignKey constraint, leaving
<table_name>__old in db schema
----------------------------------+------------------------------------
Reporter: ezaquarii | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 2.0
Severity: Release blocker | Resolution: fixed
Keywords: sqlite migration | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by johnthagen):
FWIW, I hit this bug too in Python 3.7.1, sqlite 3.26.0, and Django 2.1.4.
In my case, if I had models with `ForeignKey`s that related to each other
in reverse alphabetic order, I got errors on that looked like:
`django.db.utils.OperationalError: no such table: main.polls_cat__old`
In case it's helpful for another data point, I wrote a detailed report
here: https://github.com/beda-software/drf-writable-nested/issues/64
--
Ticket URL: <https://code.djangoproject.com/ticket/29182#comment:43>
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/067.2366bbf30eb7d418d40833595fe31736%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
