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
32095	update_or_create should utilize update_fields on update	Florian Apolloner	Sarah Boyce	"`update_or_create` should update only the fields in `default` on update, not all fields. While it is concurrency-safe to update the whole model since `update_or_create` fetches the object via `select_for_update` it is still unnecessary to re transmit all fields back to the database (probably results in more wal/binary logs written etc etc…).

In the end `update_or_create` (and most likely `get_or_create`) might be written in more efficient ways depending on the database backend -- but `update_fields` seems to be a rather low-hanging fruit.
"	Cleanup/optimization	closed	Database layer (models, ORM)	3.1	Normal	fixed		David Wobrock	Ready for checkin	1	0	0	0	0	0