id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
21212	"OneToOneField reference does not document the ""reverse"" name"	bjb@…	schacki	"https://docs.djangoproject.com/en/dev/ref/models/fields/#onetoonefield

Says OneToOneField is like ForeignKey, and does not name the reverse attribute.

ForeignKey states that the reverse attribute is called <othermodel>_set and can refer to multiple models.  The OneToOneField documentation says the reverse attribute returns a single object, but doesn't say what the reverse name is (surely not <othermodel>_set? - but if not that, then what?)

This is true for 1.5 and dev documentation - probably true for other versions as well.

It would also be nice it if explicitly stated that an instance of the other model can exist without having an instance of the model that refers to it with OneToOneField.  Eg, if you have:

Place

Restaurant
  place = OneToOneField (Place)

Then you can have a place record without a Restaurant record, but you cannot have a Restaurant record without a Place record.  This is alluded to in the Place/Restaurant example elsewhere https://docs.djangoproject.com/en/dev/topics/db/examples/one_to_one/, but could be stated in the OneToOneField documentation.


This may be related to #10227.  But until any change are implemented, I'm for documenting the actual behaviour."	Cleanup/optimization	closed	Documentation	dev	Normal	fixed	OneToOneField, reverse		Accepted	1	0	0	1	1	0