Opened 5 years ago

Closed 5 years ago

#30697 closed Bug (wontfix)

SQLite3.28 breaks django migrations.

Reported by: Osher De Paz Owned by: nobody
Component: Database layer (models, ORM) Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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

Change History (1)

comment:1 by Mariusz Felisiak, 5 years ago

Component: Uncategorized → Database layer (models, ORM)
Resolution: → wontfix
Status: new → closed
Summary: SQLite3.28 breaks django migrations → SQLite3.28 breaks django migrations.

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

Note: See TracTickets for help on using tickets.
Back to Top