---
title: "How to provide initial data for models"
version: 6.0
locale: pt-br
source: https://docs.djangoproject.com/pt-br/6.0/howto/initial-data/
canonical: https://djangodocs.dev/pt-br/6.0/howto/initial-data/
---
# How to provide initial data for models

It’s sometimes useful to prepopulate your database with hardcoded data when
you’re first setting up an app. You can provide initial data with migrations or
fixtures.

## Provide initial data with migrations

To automatically load initial data for an app, create a
[data migration](/pt-br/6.0/topics/migrations/#data-migrations). Migrations are run when setting up the
test database, so the data will be available there, subject to [some
limitations](/pt-br/6.0/topics/testing/overview/#test-case-serialized-rollback).

## Provide data with fixtures

You can also provide data using [fixtures](/pt-br/6.0/topics/db/fixtures/#fixtures-explanation),
however, this data isn’t loaded automatically, except if you use
[`TransactionTestCase.fixtures`](/pt-br/6.0/topics/testing/tools/#django.test.TransactionTestCase.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`](/pt-br/6.0/ref/django-admin/#django-admin-dumpdata). Ou, você pode escrever fixtures manualmente; “fixtures” podem ser escritas como documentos JSON, XML ou YAML (com [PyYAML](https://pyyaml.org/) installed). O [documentos de serialização](/pt-br/6.0/topics/serialization/) tem mais detalhes sobre cada um destes [formatos de serialização](/pt-br/6.0/topics/serialization/#serialization-formats).

As an example, though, here’s what a fixture for a `Person` model might look
like in JSON:

```js
[
  {
    "model": "myapp.person",
    "pk": 1,
    "fields": {
      "first_name": "John",
      "last_name": "Lennon"
    }
  },
  {
    "model": "myapp.person",
    "pk": 2,
    "fields": {
      "first_name": "Paul",
      "last_name": "McCartney"
    }
  }
]
```

E aqui a mesma “fixture” como YAML:

```yaml
- model: myapp.person
  pk: 1
  fields:
    first_name: John
    last_name: Lennon
- model: myapp.person
  pk: 2
  fields:
    first_name: Paul
    last_name: McCartney
```

Você armazenará este dado em um diretório `fixtures` dentro de sua app.

You can load data by calling [`manage.py loaddata`](/pt-br/6.0/ref/django-admin/#django-admin-loaddata)
`<fixturename>`, where `<fixturename>` is the name of the fixture file
you’ve created. Each time you run [`loaddata`](/pt-br/6.0/ref/django-admin/#django-admin-loaddata), the data will be read
from the fixture and reloaded into the database. Note this means that if you
change one of the rows created by a fixture and then run [`loaddata`](/pt-br/6.0/ref/django-admin/#django-admin-loaddata)
again, you’ll wipe out any changes you’ve made.

### Tell Django where to look for fixture files

By default, Django looks for fixtures in the `fixtures` directory inside each
app, so the command `loaddata sample` will find the file
`my_app/fixtures/sample.json`. This works with relative paths as well, so
`loaddata my_app/sample` will find the file
`my_app/fixtures/my_app/sample.json`.

Django also looks for fixtures in the list of directories provided in the
[`FIXTURE_DIRS`](/pt-br/6.0/ref/settings/#std-setting-FIXTURE_DIRS) setting.

To completely prevent default search from happening, use an absolute path to
specify the location of your fixture file, e.g. `loaddata /path/to/sample`.

> **Namespace your fixture files**
>
> Django will use the first fixture file it finds whose name matches, so if
> you have fixture files with the same name in different applications, you
> will be unable to distinguish between them in your `loaddata` commands.
> The easiest way to avoid this problem is by *namespacing* your fixture
> files. That is, by putting them inside a directory named for their
> application, as in the relative path example above.

> **See also**
>
> As “Fixtures” são também usadas pelo [testing framework](/pt-br/6.0/topics/testing/tools/#topics-testing-fixtures) para auxiliar na configuração de um ambiente de teste consistente.