#36464: TupleIn lookup uses tuple containment even if the supports_tuple_lookups
feature is disabled for right-hand-side subqueries
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: composite, primary, | Triage Stage: Accepted
key |
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
> I'm assuming we'll want some sort of low-level test against the
compiled SQL when the feature flag is false as modeled in the report.
I was thinking one thing we could do is run the `composite_pk` suite on
all backends with the feature disabled somehow. The ''fallback SQL''
should work on all backends anyway.
--
Ticket URL: <https://code.djangoproject.com/ticket/36464#comment:5>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019778e15ffd-c1b2671c-df9d-49cf-ad4a-0f225fdacf54-000000%40eu-central-1.amazonses.com.
