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
10215	"Dont rollback transaction on errors in management/loaddata in ""non-commit"" mode."	Vadim Fint	nobody	"loaddata command by default tries to use transaction for all it's work. But it accepts commit=False, which can made whole loaddata call part of outer transaction (this is usefull for call_command :)). But.. on any error - loaddata will close transaction in any way :(.

0. Start transaction
1. Create something in db
2. Call loaddata with commit=False (in try..except block -- we can have possible error and we know that)
3. Got an error while loaddata
4. Ooops.. loaddata rollbacks whole transaction, thus my changes in 1st step are gone
5. grrrrr.

But.. loaddata for easy using in non-interactive mode should also return something ""okay"" to callee, right now there is no way to determine that. But this is not covered by this ticket :).
p.s. not sure about component -- ""Core framework"" or ""django-admin.py""?"		closed	Core (Other)	dev		fixed			Design decision needed	1	0	1	0	0	0