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
35554	Model.save() positional argument parsing slightly incorrect	Adam Johnson	Adam Johnson	"Ticket #35060 introduced a deprecation pathway for positional arguments in `Model.save()`. The code introduced to match positional arguments is slightly incorrect, leading to some subtle behaviour changes:

1. Calling with extra positional arguments, such as `Model.save(False, False, None, None, None)`, no longer raises a `TypeError`.
2. Calling with positional empty `update_fields`, such as `Model.save(False, False, None, [])`, would try to save all fields, due to truthy-checking of arguments.

These are definitely edge cases, but we can easily avoid them with alternative parsing logic. PR incoming."	Bug	closed	Database layer (models, ORM)	5.1	Release blocker	fixed			Ready for checkin	1	0	0	0	0	0