#30697: SQLite3.28 breaks django migrations
-----------------------------------------+------------------------
Reporter: UnDarkle | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.11
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 |
-----------------------------------------+------------------------
It seems you've fixed it for django 2+, but it's not fixed in 1.11 (which
should still be supported according to your roadmap)
https://code.djangoproject.com/ticket/29182
since python 3.7.4 came out, the builtin sqlite library has been upgraded
and some migrations are broken (at least on windows).
{{{
query = '\n SELECT REFERRING.`resourcedata_ptr_id`,
REFERRING.`resourcedata_ptr_id` FROM `management_demore...n
WHERE REFERRING.`resourcedata_ptr_id` IS NOT NULL AND REFERRED.`id` IS
NULL\n '
params = None
def execute(self, query, params=None):
if params is None:
> return Database.Cursor.execute(self, query)
E sqlite3.OperationalError: no such table:
management_resourcedata__old
.tox\py37-django1.11\lib\site-
packages\django\db\backends\sqlite3\base.py:326: OperationalError
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30697>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.79e85f58fcbbdd9d9196e3c3ea24f830%40djangoproject.com.
