Context Navigation

Changes between Version 4 and Version 5 of Fixtures

v4	v5
49	49	The location where Django loads a fixture from might seem unintuitive. As with template files the fixtures off all applications in a project share the same namespace. If you follow [source:django/trunk/django/core/management/commands/loaddata.py?rev=9770#L79 loaddata.py] you see that Django searches for {{{ appnames/fixtures }}} and {{{ settings.FIXTURE_DIRS }}} and loads the first match. So if you use names like {{{ testdata.json }}} for your fixtures you must make sour that no other active application uses a fixture with the same name. If not, you can never be sure what fixtures you actually load.
50	50
51		Therefore it is suggested that you prefix your fixtures wit the application names, e.g. {{{ myapp/fixtures/myapp_testdata.json }}}.
	51	Therefore it is suggested that you prefix your fixtures with the application names, e.g. {{{ myapp/fixtures/myapp_testdata.json }}}.
52	52
53	53