From f91b5a7e4b2ac436b1fe3065b23217543d0f54c1 Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Sat, 9 Jan 2016 21:30:19 +0100 Subject: Fixed #26063 -- Crash when passing > 2000 params. If SQLITE_MAX_VARIABLE_NUMBER (default = 999) is changed at compile time to be greater than SQLITE_MAX_COLUMN (default = 2000), which Debian does by setting the former to 250000, Django raised an exception on queries containing more than 2000 parameters when DEBUG = True. --- docs/releases/1.9.2.txt | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.9.2.txt b/docs/releases/1.9.2.txt index 71709d0fb8..0da9cf65cd 100644 --- a/docs/releases/1.9.2.txt +++ b/docs/releases/1.9.2.txt @@ -44,3 +44,8 @@ Bugfixes * Fixed a ``QuerySet.order_by()`` crash when ordering by a relational field of a ``ManyToManyField`` ``through`` model (:ticket:`26092`). + +* Fixed a regression that caused an exception when making database queries on + SQLite with more than 2000 parameters when :setting:`DEBUG` is ``True`` on + distributions that increase the ``SQLITE_MAX_VARIABLE_NUMBER`` compile-time + limit to over 2000, such as Debian (:ticket:`26063`). -- cgit v1.3