Changes between Initial Version and Version 1 of Ticket #36473, comment 1
- Timestamp:
- Jun 19, 2025, 10:18:54 AM (3 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36473, comment 1
initial v1 1 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).1 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`) and they make assumptions with regards to `NULL` handling (composite primary keys cannot contain `NULL` values) so they should be considered internal until at least #27351 is fixed (it should be re-opened). 2 2 3 3 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).