#8562: OneToOnes + primary_key = True ... fails in Admin
--------------------------------------+-------------------------------------
Reporter: magneto | Owner: nobody
Status: new | Milestone:
Component: Admin interface | Version: SVN
Resolution: | Keywords: admin onetoone
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by magneto):
* summary: OneToOnes + Inlines fails in Admin => OneToOnes + primary_key
= True ... fails in Admin
Comment:
ok, so it has again to do with the Primary key designation that was the
issue in #7938.
If i change one of the Models to
{{{
class MooOne(models.Model):
basemoo = models.ForeignKey(BaseMoo, primary_key = True, unique =
True)
is_moo_one = models.BooleanField(default = True)
}}}
Then Editing a MooOne directly pre-populates the Dropdown menu/Raw ID text
box ...
The 'editing inline' for these of a BaseMoo also still fails
--
Ticket URL: <http://code.djangoproject.com/ticket/8562#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
