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
15578	loaddata and processing order of fixtures	Luc Saffre	Leo Suarez	"As the documentation for loaddata correctly says: ""the order in which fixture files are processed is undefined.""
That's a pity because I use fixtures to provide combinable and interdependent sets of demo data.

Would it be difficult to implement a rule for the order in which fixtures are loaded?
I'd suggest the following rule:
If there are 3 applications ""a"", ""b"" and ""c"" and you invoke 

{{{
manage.py loaddata foo bar baz
}}}

(or you specify 
{{{
fixtures = ['foo','bar','baz']
}}}

in a TestCase, then loaddata would first load all fixtures 'foo' for all applications, then all fixtures named 'bar', then all fixtures 'baz'.


"	Cleanup/optimization	closed	Documentation	1.2	Normal	fixed			Accepted	1	0	0	1	0	0