#9982: Inconsistent behavior on model save depending on whether OneToOneField
is a
primary key
-------------------------------------+-------------------------------------
Reporter: sean@… | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: OneToOneField | Triage Stage: Accepted
primary_key IntegrityError |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"85195dd23733312fa58a115490a38508a1f2bc0c" 85195dd2]:
{{{
#!CommitTicketReference repository=""
revision="85195dd23733312fa58a115490a38508a1f2bc0c"
Refs #9982 -- Added test for saving OneToOneField field after saving
related object.
Fixed in 519016e5f25d7c0a040015724f9920581551cab0.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/9982#comment:11>
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/078.d1d1a0b0b6e365023098092fcf2083e0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
