[Django] #30697: SQLite3.28 breaks django migrations

2 views
Skip to first unread message

Django

unread,
Aug 11, 2019, 4:44:02 AM8/11/19
to django-...@googlegroups.com
#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.

Django

unread,
Aug 11, 2019, 4:58:27 AM8/11/19
to django-...@googlegroups.com
#30697: SQLite3.28 breaks django migrations.
-------------------------------------+-------------------------------------
Reporter: Osher De Paz | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution: wontfix

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):

* status: new => closed
* resolution: => wontfix
* component: Uncategorized => Database layer (models, ORM)


Comment:

Unfortunately patch for #29182 doesn't qualify for a backport. Django 1.11
is in an extended support, hence it receives only security fixes.

--
Ticket URL: <https://code.djangoproject.com/ticket/30697#comment:1>

Reply all
Reply to author
Forward
0 new messages