#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 loic):
Or to give another example:
{{{
>>> Employee._meta.get_field('company).to
<class 'app.models.Company'>
>>> Employee._meta.get_field('company).one_to_many
True
}}}
Therefore I'd expect many companies when I do `employee.company`.
Technically `to` lives on `Field.rel`, and not on `Field.to` but this is
likely to go away when we introduce reverse fields. `rel` is ambiguous
because since the meta refactor it means both "the relation" and "the
reverse field".
--
Ticket URL: <https://code.djangoproject.com/ticket/24289#comment:4>
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.ee4d2c04d4626e49a51c222821cb591a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
