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
11811	No error raised on update(foreignkey=unsavedobject) on nullable fk	Afief	Aymeric Augustin	"Found this while coding at 2AM:
When there is a field that can be NULL, and you do something like this:
obj1=Obj1(...)
obj2=Obj2.objects.all().update(foreignobj=obj1)

django will assign the fields to NULL.

I'm not sure if this behaviour is made to be so by design, but it seems to me that if someone passes an unsaved object instead of None they made a mistake and django should raise an exception."	Bug	closed	Database layer (models, ORM)	1.1	Normal	fixed			Accepted	1	1	0	0	0	0