Date: Wed, 22 Apr 2020 06:41:18 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 240820] www/py-django111: SQLite backend broken after 3.26 Message-ID: <bug-240820-21822-OG4FkY3Tl0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-240820-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-240820-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240820 Kai Knoblich <kai@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://github.com/django/d | |jango/pull/11986 --- Comment #4 from Kai Knoblich <kai@FreeBSD.org> --- (In reply to rozhuk.im from comment #0) (In reply to Kubilay Kocak from comment #3) Hi, for the record here's a short overview: * The original PR #10733 with a slighty different patch (=3D diff against D= jango 2.x branch) got merged (2018-12-07) into the 2.x branch of Django but not in the 1.11 branch. * Two PRs #11610 (2019-07-30) and #11986 (2019-10-29), which contain the attached patch of this bug, were created by different users to get it merged into the Django 1.11 branch. Both PRs were rejected by upstream. Considering those facts and the following points: 1) SQLite 3.26 was introduced to the Ports tree via ports r486622 (2018-12-= 04). 2) This bug was reported nine months later after databases/sqlite3 was upda= ted to 3.26. 3) The issue with SQLite seems to be happen in some rare cases when using foreign key restraints. Upstream recommends as a workaround to rebuild the whole tables by not using migrations as described in [1]. 4) Django 1.11 is End-of-Life since April 2020 and there's already progress= in the Ports tree to switch the consumers of Django 1.11 to Django 2.2 (current LTS release), see also bug #245309. 5) I also tried to reproduce the issue with Django 1.11 and migrations from SQLite 3.25 to SQLite 3.31 but without any luck so far. Originally I was under the impression that the original PR #10733 was merged into all branches of Django but on further review it came to light that this isn't the case. After discussing the whole situation with koobs@ we believe the best way is= to leave the www/py-django111 port in its current state. because Django 1.11 is End-of-Life, the issue isn't reproducible and there's a workaround as noted= at 3) which might be another reason why upstream didn't backport that patch for Django 1.11. -- [1] https://docs.djangoproject.com/en/2.1/releases/2.0/#foreign-key-constraints= -are-now-enabled-on-sqlite --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240820-21822-OG4FkY3Tl0>