#24289: Is usage of many_to_one and one_to_many terms confusing for relation
flags?
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8alpha1
(models, ORM) |
Severity: Release blocker | 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 collinanderson):
* cc: cmawebsite@… (added)
Comment:
I believe the precedent that Russ is talking about is `ManyToOneRel` (ie
`author.book_set`), which I also think should be a one_to_many.
ForeignKeys are One-to-many, based on the interpretation that there is
"one" value on the side that defines them, and "many" on the other side.
The UI for this is a dropdown where for a book, you choose (one) of
"many" (possible) authors. However, once the value is chosen and the
relationship is set, there's only one author.
--
Ticket URL: <https://code.djangoproject.com/ticket/24289#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.1571667daf8a6f7f036df39f9a2fbe8a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
