#36473: Usage of new tuple_lookups in 5.2
-------------------------------------+-------------------------------------
Reporter: Julien Chaumont | Owner: (none)
Type: Uncategorized | Status: new
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: tuple_lookups | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Short answer is that tuple lookups are not ready for prime time for
anything except usage against composite primary keys as we don't have a
way to represent generic composite fields (think of the equivalent of
`tuple[Field]` as an `output_field`) so they should be considered internal
until at least #27351 is fixed (it should be re-opened).
Happy to answer your question in more details
[https://forum.djangoproject.com/c/internals/orm/9 on the forum] but I'll
close now as we don't use this ticket tracker to answer question (it's for
actionable units of work).
--
Ticket URL: <https://code.djangoproject.com/ticket/36473#comment:1>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019788b9677d-bdf19648-eb6e-418d-89db-cc3d8458d7c1-000000%40eu-central-1.amazonses.com.
