It’s sometimes useful to pre-populate your database with hard-coded data when\nyou’re first setting up an app. You can provide initial data with migrations or\nfixtures.
\nIf you want to automatically load initial data for an app, create a\ndata migration. Migrations are run when setting up the\ntest database, so the data will be available there, subject to some\nlimitations.
\nYou can also provide data using fixtures, however, this data isn’t loaded\nautomatically, except if you use TransactionTestCase.fixtures.
A fixture is a collection of data that Django knows how to import into a\ndatabase. The most straightforward way of creating a fixture if you’ve already\ngot some data is to use the manage.py dumpdata command.\nOr, you can write fixtures by hand; fixtures can be written as JSON, XML or YAML\n(with PyYAML installed) documents. The serialization documentation has more details about each of these supported\nserialization formats.
As an example, though, here’s what a fixture for a simple Person model might\nlook like in JSON:
[\n {\n "model": "myapp.person",\n "pk": 1,\n "fields": {\n "first_name": "John",\n "last_name": "Lennon"\n }\n },\n {\n "model": "myapp.person",\n "pk": 2,\n "fields": {\n "first_name": "Paul",\n "last_name": "McCartney"\n }\n }\n]\n그리고 YAML로 된 동일한 fixture 가 있습니다.
\n- model: myapp.person\n pk: 1\n fields:\n first_name: John\n last_name: Lennon\n- model: myapp.person\n pk: 2\n fields:\n first_name: Paul\n last_name: McCartney\nYou’ll store this data in a fixtures directory inside your app.
Loading data is easy: just call manage.py loaddata\n<fixturename>, where <fixturename> is the name of the fixture file\nyou’ve created. Each time you run loaddata, the data will be read\nfrom the fixture and re-loaded into the database. Note this means that if you\nchange one of the rows created by a fixture and then run loaddata\nagain, you’ll wipe out any changes you’ve made.
By default, Django looks in the fixtures directory inside each app for\nfixtures. You can set the FIXTURE_DIRS setting to a list of\nadditional directories where Django should look.
When running manage.py loaddata, you can also\nspecify a path to a fixture file, which overrides searching the usual\ndirectories.