#8562: OneToOnes + primary_key = True ... fails in Admin
--------------------------------------+-------------------------------------
Reporter: magneto | Owner: nobody
Status: new | Milestone: 1.0
Component: Admin interface | Version: SVN
Resolution: | Keywords: admin onetoone
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by kmtracey):
* stage: Unreviewed => Accepted
Comment:
Fist bug I see here is the !KeyError on an attempt to save a model with a
pre-existing inline-edited !OneToOne related object.
Second is the fact that the widgets (raw or default) for the related field
are not populated on the change page for the objecting containing the
!OneToOne field.
Both are fixed by the 8562_primary_uniques.diff, but I am not at all
familiar with the code involved here so have no idea of the correctness of
the fix beyond it does fix the observed symptoms.
What's not a bug is the Admin failing to create the inline-edited object
in the case where you made no changes to any of its initial values. Since
the admin doesn't have an explicit 'add' checkbox for adding new inlines,
it relies on trying to determine if anything changed between the form as
initially created and what is submitted. If they're identical, no new
related object is created.
--
Ticket URL: <http://code.djangoproject.com/ticket/8562#comment:7>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
