﻿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
21134	Documentation for transaction.atomic needs more explicit warning about catching DatabaseErrors	RichardOfWard	Aymeric Augustin	Catching a database error inside transaction.atomic and then subsequently issuing more database commands before the end of the atomic block leads to a silent implicit rollback of the subsequent commands in Atomic's  `__exit__`, even when there is no current exception. When using PostrgeSQL an InternalError is raised by the db when these subsequent commands are attempted as PostgreSQL disallows this behaviour. MySQL and SQLite3 are less strict and so no error is raised, leading to confusing and hard to diagnose behaviour. The current documentation doesn't highlight this potential pitfall.	Cleanup/optimization	closed	Database layer (models, ORM)	1.6-beta-1	Release blocker	fixed			Ready for checkin	1	0	0	0	0	0
