#9982: Inconsistent behavior on model save depending on whether OneToOneField
is a
primary key
---------------------------------------------------+------------------------
Reporter: [email protected] | Owner:
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
OneToOneField primary_key IntegrityError
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* owner: mtredinnick =>
* status: assigned => new
* milestone: 1.2 =>
Comment:
Moving off the 1.2 milestone. As noted in the first comment, this should
be raising an error in the case that appears to work, in the best case. So
it's not a case of something not working that should.
--
Ticket URL: <http://code.djangoproject.com/ticket/9982#comment:5>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
