#5929: Allow Fields to use multiple db columns (complex datatypes)
-------------------------------------+-------------------------------------
Reporter: Daniel | Owner: HAMA
Poelzleithner | Barhamou
Type: New feature | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* resolution: duplicate =>
* status: closed => new
Comment:
Reopening because we have agreement on removing the `Query.output_field`
"first column only" limitation described in comment:35, even if only for
the internals at first. Pravin is working on this as a prerequisite for
#37115.
Then another commit could tackle generalizing `CompositePrimaryKey` to
make use of that new `CompositeField` (comment:36). We may want to merge
both commits at the same time, to make sure the prep work was suitable
enough.
Finally, we might have a separate commit for finalizing and documenting
using `CompositeField` in a model definition, but this may require a lot
of other subsystems to be audited, like the admin, forms, and serializers,
and those parts aren't a prerequisite for #37115.
--
Ticket URL: <https://code.djangoproject.com/ticket/5929#comment:41>
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/0107019ecc822921-dedb4cda-df92-4456-833b-c013e27f2d15-000000%40eu-central-1.amazonses.com.
