#36473: Usage of new tuple_lookups in 5.2 -------------------------------------+------------------------------------- Reporter: Julien Chaumont | Type: | Uncategorized Status: new | Component: Database | layer (models, ORM) Version: 5.2 | Severity: Normal 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 -------------------------------------+------------------------------------- Hi,
As a part of the composite primary key feature, django 5.2 includes new utilities such as [https://github.com/csirmazbendeguz/django/blob/main/django/db/models/fields/tuple_lookups.py#L375 `TupleIn` or `TupleGreaterThan`]. From what I've seen, these helpers can be used on any columns, and not necessarily on composite primary keys. However, they're not mentioned anywhere in [https://docs.djangoproject.com/en/5.2/search/?q=tuplein the documentation]. Can you clarify if they are considered internals, or if they can be considered as part of Django's API? -- Ticket URL: <https://code.djangoproject.com/ticket/36473> 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/01070197888ceb3e-300bf010-a009-43b6-9371-e1aa0d3829aa-000000%40eu-central-1.amazonses.com.