#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: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Loic Bistuer <loic.bistuer@…>):
In [changeset:"20b621eb3c3dd947a4fe77a2a11264b9072ef25c"]:
{{{
#!CommitTicketReference repository=""
revision="20b621eb3c3dd947a4fe77a2a11264b9072ef25c"
[1.8.x] Fixed #24289 -- Reversed usage of Field.many_to_one and
one_to_many.
Thanks Carl Meyer and Tim Graham for the reviews and to all involved
in the discussion.
Backport of 18c0aaa9123579375294fcc4a8ee7e3530176b88 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24289#comment:24>
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.c0add024663a611a2f7d0cd4a0b23392%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
