#34125: Limiting QuerySet crashes on union() with a single non-empty query
-------------------------------------+-------------------------------------
Reporter: Stefan Hammer | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"c2cc80756b8949cdd87b88bbfdfee698ced441e0" c2cc807]:
{{{
#!CommitTicketReference repository=""
revision="c2cc80756b8949cdd87b88bbfdfee698ced441e0"
Fixed #34125 -- Fixed sliced QuerySet.union() crash on a single non-empty
queryset.
The bug existed since sliced query union was added but was elevated to
query union slices by moving the .exists() optimization to the compiler
in 3d734c09ff0138441dfe0a59010435871d17950f.
Thanks Stefan Hammer for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34125#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070184229eb987-6e783a2c-599b-4e27-aad3-c3ebe0370122-000000%40eu-central-1.amazonses.com.
