It’s sometimes useful to prepopulate your database with hard-coded data when\nyou’re first setting up an app. You can provide initial data with migrations or\nfixtures.
\nTo 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,\nhowever, this data isn’t loaded automatically, except if you use\nTransactionTestCase.fixtures.
Uma fixture é uma coleção de dados que o Django sabe como importar para o banco de dados. A maneira mais fácil de criar uma “fixture” se você já tem algum dado é usar o comando manage.py dumpdata. Ou, você pode escrever fixtures manualmente; “fixtures” podem ser escritas como documentos JSON, XML ou YAML (com PyYAML installed). O documentos de serialização tem mais detalhes sobre cada um destes formatos de serialização.
As an example, though, here’s what a fixture for a Person model might look\nlike 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]\nE aqui a mesma “fixture” como YAML:
\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\nVocê armazenará este dado em um diretório fixtures dentro de sua app.
You can load data by calling 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 reloaded 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 for fixtures in the fixtures directory inside each\napp, so the command loaddata sample will find the file\nmy_app/fixtures/sample.json. This works with relative paths as well, so\nloaddata my_app/sample will find the file\nmy_app/fixtures/my_app/sample.json.
Django also looks for fixtures in the list of directories provided in the\nFIXTURE_DIRS setting.
To completely prevent default search from happening, use an absolute path to\nspecify the location of your fixture file, e.g. loaddata /path/to/sample.