#14368: Reverse relation attribute for OneToOneField fails when set to None
-------------------------------------+-------------------------------------
Reporter: gsakkis | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: OneToOneField, bug | 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 Tim Graham <timograham@…>):
In [changeset:"b646fbe4a77c10314ffcac31ff2f10a42e69c220" b646fbe]:
{{{
#!CommitTicketReference repository=""
revision="b646fbe4a77c10314ffcac31ff2f10a42e69c220"
[1.9.x] Fixed #14368 -- Allowed setting a reverse OneToOne relation to
None.
Backport of 384ddbec1b73a4636f234da3894fde8f8420bb63 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/14368#comment:17>
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/065.99a9beb847836986af4950bc1115e0e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
