Changes between Initial Version and Version 4 of Ticket #28378
- Timestamp:
- Jul 9, 2017, 1:12:37 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28378
- Property Severity Normal → Release blocker
- Property Triage Stage Unreviewed → Accepted
- Property Cc added
-
Ticket #28378 – Description
initial v4 1 1 Similar and followup to ticket #28293. Tested on Django 1.11.3. 2 2 3 As QuerySet.union() uses the SQL UNION operator, I would expect "SET1 UNION <EMPTY SET>" to result in SET1. If the empty set is the results of [https://github.com/django/django/blob/5b450b84e14f42302f58ec1f15a67a368e64d85c/django/db/models/sql/where.py#L97 EmpytResultSet being raised], the `.u ion()` result is an empty set, not SET1.3 As QuerySet.union() uses the SQL UNION operator, I would expect "SET1 UNION <EMPTY SET>" to result in SET1. If the empty set is the results of [https://github.com/django/django/blob/5b450b84e14f42302f58ec1f15a67a368e64d85c/django/db/models/sql/where.py#L97 EmpytResultSet being raised], the `.union()` result is an empty set, not SET1. 4 4 5 5 Example test case: