Welcome back! In our previous lesson, we explored how to implement a one-to-one relationship in Django by linking a Note model to an existing Todo model. This relationship allowed each Todo item to have a unique note associated with it.

Today, we will advance to another fundamental concept in database schema design: the one-to-many relationship. This type of relationship is essential in many real-world scenarios, such as associating multiple tasks with a single project or user. By the end of this lesson, you will learn how to define a one-to-many relationship in Django, serialize the data, and perform CRUD (Create, Read, Update, Delete) operations through a REST API.

Let's imagine that we want to store task groups as a separate model to bind more information to a group, such as a group's access rights or settings. In this case, each Group instance can have multiple corresponding Todo instances (as each group stores multiple items), but each Todo instance can be inside only one group. This is called a one-to-many relationship.

Here's how you can define this in models.py:

1. Group Model:

   • name: A character field to hold the group name.

2. Todo Model:

   • group: A foreign key to the Group model, establishing a one-to-many relationship. If a Group is deleted, all the associated Todo tasks will be deleted (on_delete=models.CASCADE). This field can be null or left blank, allowing creation of Todo instances without a specified group.

This setup allows each Todo to be associated with one Group, but each Group can have multiple Todos.

In SQL databases, a one-to-many relationship is implemented using a foreign key. The foreign key field in the child table references the primary key of the parent table. In our case, the Todo table has a foreign key referencing the Group table. Here’s an illustration of how these tables might look:

Here, we have two tasks (1 and 2) that belong to one group (they both have group_id = 1).

Serializers help convert complex data types, such as querysets and model instances, into native Python data types that can then be easily rendered into JSON and vice versa.

Here's how to create serializers for the Group and Todo models in serializers.py:

1. GroupSerializer:

   • This serializer converts the Group model into JSON format and vice versa. The fields being serialized are id and name.

2. TodoSerializer:

   • This serializer handles the Todo model. By using fields = '__all__', it includes all fields of the Todo model for serialization and deserialization.

Serializers are crucial for ensuring that data sent to and received from the API is in the correct format.

Fixtures are a convenient way to add sample data to your tests. They allow you to create a consistent testing environment.

Here's a fixture that will create initial data to test our one-to-many relationship, to be placed in fixtures/one_to_many.json:

1. Group:

   • Creates a group with pk (primary key) of 1 and the name "Group A".

2. Todo:

   • Adds a task associated with "Group A". It is not completed, has priority 1, and references the created group using group: 1.

Fixtures help streamline testing by loading predefined sets of data into the database.

It is important to test your models and their relationships to ensure they work as intended. Here is a test case in tests.py to check if a Todo item has an associated Group:

This test checks if the Todo item has an associated Group and verifies the group's name. It uses the fixture data we defined earlier.

The following test case in tests.py goes further to create new Group and Todo records and verify their relationships:

This test case creates a new Group named 'Group B' and associates two new Todo items with this group. It verifies the creation by checking the status codes of the responses. The test then retrieves the Todo items from the database and asserts that they are associated with the correct group.

Testing ensures the integrity and correctness of your application's relationships and functionalities.

In this lesson, we delved into implementing a one-to-many relationship between Group and Todo models in Django. We covered:

• Defining the models and their relationships,
• How one-to-many relationships are stored in SQL tables,
• Creating serializers to handle the data,
• Using fixtures to pre-load data for testing,
• Writing test cases to ensure the integrity of the relationship,
• Setting up views and URLs for CRUD operations.

Now, it's time to put this knowledge into practice. Proceed to the exercises that follow to reinforce your understanding and gain hands-on experience. Happy coding!