#373: Add support for multi-columns fields.
-------------------------------------+-------------------------------------
Reporter: Jacob | Owner: Csirmaz
| Bendegúz
Type: New feature | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: database | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Ben Finney):
Replying to [comment:201 Ben Finney]:
> The implementation of an *individual field* with multiple columns, is
not the same thing, and in principle is not required. (In practice it may
be one feasible implementation, but it is not necessarily related to this
one.) There is an existing issue (#5929) requesting multi-column fields,
which I argue should be re-opened since it is a distinct issue.
(Yes, I'm aware there was a discussion opened on a different platform to
address this. That discussion is not open to anyone who can't use a GitHub
account to authenticate, so I raise the matter here where I can
participate.)
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:202>
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/01070192fec2ea2c-57d9064e-9535-4562-8534-3735186e9996-000000%40eu-central-1.amazonses.com.
