#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:197 Csirmaz Bendegúz]:
> It would be best to limit the scope of this ticket to the original goal
of implementing ''**composite primary keys**''.
I agree with this. Can we please re-title this issue, back to “Add support
for multiple-column primary keys”?
Csirmaz has an implementation of a composite primary key, and it correctly
refers to this issue (#373) requesting composite primary key.
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.
I ask that the title change, made last year (see
https://code.djangoproject.com/ticket/373?replyto=197#comment:162 ) should
be reversed, as Csirmaz describes.
--
Ticket URL: <https://code.djangoproject.com/ticket/373#comment:201>
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/01070192febfff7d-813b8f96-013f-40bd-90b4-bb0a1ba799a6-000000%40eu-central-1.amazonses.com.
