#2948: Better OneToOneField handling in Admin Interface desired
-----------------------------------------------+----------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: new | Milestone:
Component: Admin interface | Version: newforms-admin
Resolution: | Keywords: nfa-someday
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------+----------------------------
Changes (by [EMAIL PROTECTED]):
* cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] (added)
Comment:
From what I can tell, the admin now has a "+" next to the Select for a
OneToOneField. The behavior the reporter talks about, with regard to
having the parent model's fields in the edit page for the child, is how
newforms-admin handles multi-table-inheritance relationships. The only
potential issue that might still exist is the inability for the framework,
in general, to handle creating a child model instance against an existing
parent, a la #7623. That said, I'd say this ticket could probably be
closed.
--
Ticket URL: <http://code.djangoproject.com/ticket/2948#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
