From 84927e110e813c3bea6a600e4474eb577e15f2b9 Mon Sep 17 00:00:00 2001 From: Francesco Panico Date: Wed, 18 Jan 2023 22:42:53 +0000 Subject: [4.2.x] Fixed #34267 -- Fixed sliced QuerySet.union() crash. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Regression in 3d734c09ff0138441dfe0a59010435871d17950f. Thanks Raphaël Stefanini for the report. Backport of cc8aa6bf9c127a493e6dd005012b9e6397b3f319 from main --- django/db/models/sql/compiler.py | 3 --- 1 file changed, 3 deletions(-) (limited to 'django/db/models/sql') diff --git a/django/db/models/sql/compiler.py b/django/db/models/sql/compiler.py index 97ecd58bdd..7c433b3f06 100644 --- a/django/db/models/sql/compiler.py +++ b/django/db/models/sql/compiler.py @@ -532,15 +532,12 @@ class SQLCompiler: "ORDER BY not allowed in subqueries of compound statements." ) elif self.query.is_sliced and combinator == "union": - limit = (self.query.low_mark, self.query.high_mark) for compiler in compilers: # A sliced union cannot have its parts elided as some of them # might be sliced as well and in the event where only a single # part produces a non-empty resultset it might be impossible to # generate valid SQL. compiler.elide_empty = False - if not compiler.query.is_sliced: - compiler.query.set_limits(*limit) parts = () for compiler in compilers: try: -- cgit v1.3