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
15124	BooleanField should not use False as default (unless provided)	Andrew Badr	Aymeric Augustin	"Steps to repro:
1) Make a Model with a BooleanField with no default
2) Instantiate that model with no initial value
3) The value of the BooleanField on that instance is False

Expected behavior:
3) The value of the BooleanField on that instance is None

Guessing a value for the field is wrong. Attempting to save a model with a non-null field without providing a value for that field should be an error. (Postgres of course throws an error if you try to insert a row with no value for a required bool field.) It's ok for CharFields with blank=True to default to the empty string, because that's semantically the lack of a value for the field. However, True and False are equals; False is not the lack of a value.

Note the existence of the opposite ticket, #2855, which was wontfix'd then apparently silently ""fixed"" at some point."	Bug	closed	Database layer (models, ORM)	1.4-alpha-1	Normal	fixed		andrewbadr.etc@… Łukasz Rekucki to.chomik@… lpiatek botondus@…	Accepted	1	0	0	0	0	0