#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 Tony S Yu):
The backport for the fix to Django 1.11 was closed. I commented on that
ticket, but for visibility, I'll comment here as well.
This issue makes it difficult to test libraries supporting both Django
1.11 and Django 2.2 on a single Centos server (without hacks to upgrade
supported sqlite versions):
- Centos 7 supports sqlite3 3.7.17 (see
[https://rpms.remirepo.net/rpmphp/zoom.php?rpm=sqlite EL-7 here])
- Centos 8 supports sqlite3 3.26.0 (see
[https://rpms.remirepo.net/rpmphp/zoom.php?rpm=sqlite EL-8 here])
Our team runs internal libraries on Centos servers using tox to test
against various versions of dependencies. The current version
incompatibilities mean that Django 1.11 tests of a library must run on
Centos 7 and tests for Django 2.2 must run on Centos 8.
--
Ticket URL: <https://code.djangoproject.com/ticket/29182#comment:48>
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/067.b23d64cc2c97e522454c8936538b8b2e%40djangoproject.com.
