Changes between Version 10 and Version 11 of Fixtures

Timestamp:

Jul 18, 2016, 11:08:21 PM (8 years ago)

Author:

Daniel Brotsky

Comment:

Update the namespacing recommendation to be consistent with that for templates.

Fixtures

@@ -49 +49 @@
 The location where Django loads a fixture from might seem unintuitive. As with template files, the fixtures of 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 sure that no other active application uses a fixture with the same name. If not, you can never be sure what fixtures you actually load.
 
-Therefore it is suggested that you prefix your fixtures with the application names, e.g. {{{ myapp/fixtures/myapp_testdata.json }}}.
+Therefore it is suggested that you qualify your fixtures with the name of the associated application.  One strategy for this is to use the application name as a filename prefix, as in {{{myapp/fixtures/myapp_testdata.json}}}.  Another strategy, which is consistent with that recommended for templates in the Django tutorial, is to put your application fixtures in a application-named subdirectory, as in {{{myapp/fixtures/myapp/testdata.json}}}.  Both of these conventions work well with {{{loaddata}}}.
 
 
@@ -56 +56 @@
 [http://www.djangoproject.com/documentation/models/fixtures/]
 [http://www.djangoproject.com/documentation/testing/#fixtures]
+[https://docs.djangoproject.com/en/1.9/intro/tutorial03/]