Changes between Version 15 and Version 16 of Fixtures

Timestamp:

Feb 24, 2021, 12:58:52 PM (4 years ago)

Author:

Elena Williams

Comment:

Removing outdated (erroneous) docs

Fixtures

@@ -1 +1 @@
 = Fixtures =
 
-Deprecated, use https://docs.djangoproject.com/en/2.2/howto/initial-data/
-
-''This is a very simple example. Please read something more complex if you need.'' 
-
-Fixtures are very powerful to play with your database sample data during development process.
-After each '''python manage.py flush <myapp>''' command you need to populate database with sample data again and again using admin interface. It's quite boring, isn't it?
-With fixtures our life became more comfortable and easy. Look at this example.
-Lets imagine that you have some data in db. We can dump it, even if your models have ForeignKeys or any kind of *To* relations.
-
-First we need to define fixtures dir in settings file:
-
-{{{
-FIXTURE_DIRS = (
-   '/path/to/myapp/fixtures/',
-)
-}}}
-
-Lets dump our data:
-
-{{{
-cd /path/to/my_project
-python manage.py dumpdata --format=json myapp > /path/to/myapp/fixtures/initial_data.json
-}}}
-
-Reset:
-
-{{{
-python manage.py reset myapp
-
-You have requested a database reset.
-This will IRREVERSIBLY DESTROY any data for
-the "myapp" application in the database "mydb".
-Are you sure you want to do this?
-
-Type 'yes' to continue, or 'no' to cancel: yes
-}}}
-
-Now we have clean DB, lets populate it with our sample data:
-
-{{{
-python manage.py syncdb
-Loading 'initial_data' fixtures...
-Installing json fixture 'initial_data' from '/path/to/myapp/fixtures/'.
-Installed 24 object(s) from 1 fixture(s)
-}}}
-
-== Fixture loading ==
-
-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 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 and static files in the Django documentation, 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}}}.
+Deprecated, use https://docs.djangoproject.com/en/3.2/howto/initial-data/
 
 
 Links: \\
 [http://en.wikipedia.org/wiki/JSON] \\
-[https://docs.djangoproject.com/en/2.1/howto/initial-data/] \\
-[https://docs.djangoproject.com/en/2.1/topics/testing/tools/#fixture-loading] \\
-[https://docs.djangoproject.com/en/2.1/intro/tutorial03/] \\
-[https://docs.djangoproject.com/en/2.1/howto/static-files/]
+[https://docs.djangoproject.com/en/3.2/howto/initial-data/] \\
+[https://docs.djangoproject.com/en/3.2/topics/testing/tools/#fixture-loading] \\
+[https://docs.djangoproject.com/en/3.2/intro/tutorial02/] \\
+[https://docs.djangoproject.com/en/3.2/howto/static-files/]