#24289: Is usage of many_to_one and one_to_many terms confusing for relation 
flags?
-------------------------------------+-------------------------------------
     Reporter:  akaariai             |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.8alpha1
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  invalid
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by freakboy3742):

 For the record - This came up during the meta refactor work as well. I
 agree it's confusing. But the thing is, *either* way is going to confuse
 someone.

 As currently defined, 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. However, it's easy to look at it the other
 way, and say that a ForeignKey is defining the fact that there where it is
 defined, it's going to point to "many" objects, and on the other side, it
 will point to "one" object.

 It's worth noting that this same confusion exists in various
 [http://en.wikipedia.org/wiki/Entity–relationship_model#Cardinalities
 Entity-Relationship diagram notations] - the side on which you put the
 visual "many" varies (c.f. Martin/Crow foot and IDEF1X notation).

 So, for me, this is a bikeshed; however, it's a bikeshed with a precedent
 that goes back 10 years, so I'd be against changing it.

--
Ticket URL: <https://code.djangoproject.com/ticket/24289#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.438ff22bfd6757c17ed14f55601de249%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to