#27351: Add support for composite fields
-------------------------------------+-------------------------------------
Reporter: Victor Porton | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => wontfix
* status: new => closed
Comment:
I think we need to update the description here to be clear on what we are
trying to achieve for this ticket before reopening and have a clear plan
on the API
The original description mentions interactions with forms for example
whereas the solution to #373 excludes forms and #36473 is more about tuple
lookups being used beyond `CompositePrimaryKeys` (again not really to do
with forms)
It seems this ticket has a very old draft DEP
(https://github.com/django/deps/blob/main/draft/0192-standalone-composite-
fields.rst) which needs quite a bit of love to agree on the API given the
solution for #373
I think once there is a clear idea of what we want to achieve and
agreement that this is a useful feature (potentially having the DEP
approved) then we can proceed
--
Ticket URL: <https://code.djangoproject.com/ticket/27351#comment:8>
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/010701978d412a0a-221522a6-0cbb-4667-9b61-fbb576387b1c-000000%40eu-central-1.amazonses.com.
