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
36075	Field.primary_key documentation should details its interaction with CompositePrimaryKey	Simon Charette	Simon Charette	"A particular focus should be put on the fact that the flag will and should only be set to `True` if the field is the single member of the primary key. When a composite primary is defined on the model this flag will be `False` for all the fields defined on the model and `_meta.pk_fields` (which should be documented) should be used instead to build composite primary key ready third-party application.

In other words, it should be made clear that code that relies solely on `Field.primary_key` is not composite primary key ready and that `_meta.pk_fields` should be used instead. I feel like this is something that should be clearly pointed out in the composite primary key documentation on how to make reusable app code composite primary key ready."	Cleanup/optimization	closed	Documentation	dev	Release blocker	fixed		Csirmaz Bendegúz	Ready for checkin	1	0	0	0	0	0