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
25879	Uncertainty about constraint checks during fixture loading	pascal chambon	nobody	"I've encountered this paragraph in docs :

{{{
https://docs.djangoproject.com/en/1.9/ref/django-admin/#what-s-a-fixture

Note that the order in which fixture files are processed is undefined. However, all fixture data is installed as a single transaction, so data in one fixture can reference data in another fixture. If the database backend supports row-level constraints, these constraints will be checked at the end of the transaction.
}}}

However, from my experience, heavily used DBs like MySQL do not have deferred constraint checking :
http://stackoverflow.com/a/5014744/345876

So if fixtures are loaded in undefined ordered, tehse references might trigger referential integrity errors on these DB engines.

Are there things I'm missing here, or shouldn't we add a note on this ?
"	Bug	closed	Documentation	1.9	Normal	duplicate			Unreviewed	0	0	0	0	0	0