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
28222	Django 1.11 update_or_create field validation results in different behaviours between create and update_or_create	Alex Mykyta	nobody	"This is an issue related to #27118. Anthony King commented on it but that issue is closed so I am opening a new one. The field validation introduced in 1.11 `update_or_create` will throw a `FieldError` if a `defaults` argument contains a value that is set through an `@property.setter` on that model. On the other hand `create` continues to function correctly. Ideally they'd behave consistently. 

Here is an example https://dpaste.de/UORC"	Bug	new	Uncategorized	1.11	Normal		1.11		Unreviewed	0	0	0	0	0	0