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
36100	get_next_by_FIELD() check for unsaved objects should account for composite primary keys	Jacob Walls	Jacob Walls	"[https://github.com/django/django/pull/19050 PR] to keep the check for unsaved objects at the top of `get_next_by_FIELD()` compatible with unsaved objects having composite primary keys.

More of a cleanup (?), since ValueError was still being raised at the ORM level:
{{{
AssertionError: 'get_next/get_previous cannot be used on unsaved objects.' not found in 'Cannot use None as a query value'
}}}"	Cleanup/optimization	closed	Database layer (models, ORM)	dev	Normal	fixed			Ready for checkin	1	0	0	0	1	0