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
18223	Database commit behavior is confusingly documented	philipn	mateusgondim	"Reading https://docs.djangoproject.com/en/dev/ref/databases/:

Transaction handling

By default, Django starts a transaction when a database connection is first used and commits the result at the end of the request/response handling. The PostgreSQL backends normally operate the same as any other Django backend in this respect.

Then reading https://docs.djangoproject.com/en/dev/topics/db/transactions/:

Django’s default behavior is to run with an open transaction which it commits automatically when any built-in, data-altering model function is called. For example, if you call model.save() or model.delete(), the change will be committed immediately.

-----

https://docs.djangoproject.com/en/dev/topics/db/transactions/ describes the current behavior.  It seems like the other documentation should be updated to reflect this."	Uncategorized	closed	Documentation	1.3	Normal	fixed			Accepted	1	0	0	0	0	0