Better OneToOneField handling in Admin Interface desired

[wam-djangobug@…]

Currently, a one to one relationship renders as a drop down box to select a instance of the related object type. If no object exists of the related type exists, the drop down box is empty with no easy way to create the object. There is no plus mark like there is for ForeignKey.

At the very least, I feel a Plus mark in the user interface associated with the OneToOneField is necessary to make the admin interface usable.

Ideally, since this is a OneToOne relationship, the fields for the related class could be brought directly into the admin interface of the object "extending" the "base" object. I tried specifying edit_inline in my OneToOne field; however, that seemed to want to put my extending class into admin interface of the extended class. If someone creates an object with a OneToOneField, then they are almost certainly want to know and be able to edit the field values of the object that is being extended.

[Malcolm Tredinnick]

Just in case anybody wants to work on this too soon: OneToOne has been slightly refactored on the queryset-refactor branch, so if any of these changes need altering of the OneToOneField code, some coordination will be required (e.g. wait until after the merge).

[brooks.travis@…]

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.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Aymeric Augustin]

Revert accidental batch modification.

[Tim Graham]

Closing per comment #4.