Fixtures in Django

Django comes with a simple way to load and dump data from the database into files that are called fixtures. The resulting data structure includes information about the model and its fields for Django to be able to load it into the database.

Fixtures are commonly used for several purposes:

1. Populating Initial Data: Fixtures allow you to populate your database with initial data required for your application to function properly. This can include default user accounts, configuration settings, or any other data needed at the start.

2. Testing: Fixtures are often used in testing to ensure that tests have consistent data to work with. By loading a predefined set of data before running tests, you can ensure that your tests are predictable and reproducible.

3. Seeding Data: In some cases, you might want to preload a database with sample data for demonstration purposes or to provide users with some initial content.

Sometimes you have some data in your development database while playing with your Django Web app, and maybe you want to save these data to use in production. Maybe you want to save these data before deleting the database to switch (Ex: from bd.sqlite3 to PostgreSQL) to a new one and again you do not want to lose the data. You want to download all the data from the database and save them into a JSON file to upload later. I think you got it!

To see all the data in the terminal type the following:

py manage.py dumpdata catalog --indent=2

Note the --indent=2 flag showing the data on a readable json format, so you can ommit it if you want to: py manage.py dumpdata catalog

To redirect (copy) the "data dump" into a new file named catalog.json:

py manage.py dumpdata catalog --indent=2 > catalog.json

To read the data in your terminal: cat catalog.json

(OPTIONAL) To remove the sqlite3 file named db.sqlite3 file: rm db.sqlite3

To perform the migrations again to get a new sqlite3 database : py manage.py migrate

Now it is time to take the serialize data create by the dumpdata command (catalog.json), and load it into the new database we will use the "loaddata" command:

py manage.py loaddata catalog.json

Note 1: 

Sometime you may have an error with the content-type while tryin to load the data, if you've face this error you can exlude it by doing the following:

py manage.py dumpdata --indent=2 --exclude contenttypes > catalog.json

Note 2: 

Sometime you may have an error with the auth-permission and the content-type while tryin to load the data, if you've face this error you can exlude it by doing the following:

py manage.py dumpdata --indent=2 --exclude auth.permission --exclude contenttypes > catalog.json

BEST PRACTICE:
We can Associate data fixtures with a Django App. By doing so we can load data base on the app name rather than on a file name. This help to create a shipable third party app that require some data associated with the models.

To do so:
    1. Create a fixture directory named "fixtures" inside the django app you want to   

    2. And run the following:

py manage.py dumpdata catalog --indent=2 > catalog/fixtures/catalog_data.json

or: 

py manage.py dumpdata blog --indent=2 --output=catalog/fixtures/catalog_data.json

(OPTIONAL): You can move the file created by dumpdata into the fixtures directory if you already have it
for example: the catalog.json file. Or create it into the fixtures directory.
    
(OPTIONAL) Open the terminal and remove the db.sqlite3 file: rm db.sqlite3

Or: you can generate an empty migration file in your app's migrations directory with the following command:

python manage.py makemigrations --empty your_app_name

Now you have to perform the migrations again: py manage.py migrate

Load the data simply by specify the app name: py manage.py loaddata catalog

Note 3: 
By default, Django looks for files in the fixtures/ directory of each application, but you can specify
the complete path to the fixture file for the loaddata command. You can also use the FIXTURE_DIRS
setting to tell Django additional directories to look in for fixtures.

Conclusion:
Fixtures play a crucial role in Django development, particularly for setting up initial data and ensuring consistent testing environments. However, as your application evolves, you might find yourself relying more on data migrations and other mechanisms for managing changes to your database schema and data.