OneToOneField for one-to-one in Django - Step-by-Step Execution

Concept Flow - OneToOneField for one-to-one

Define Model A

↓

Define Model B with OneToOneField to Model A

↓

Create instance of Model A

↓

Create instance of Model B linked to Model A

↓

Access Model B from Model A

↓

Access Model A from Model B

This flow shows how two models are linked one-to-one using OneToOneField, allowing access from each side.

Execution Sample

Django

class Profile(models.Model):
    user = models.OneToOneField(User, on_delete=models.CASCADE)
    bio = models.TextField()

p = Profile.objects.create(user=u, bio='Hello')

Defines a Profile linked one-to-one to a User, then creates a Profile instance linked to a User instance.

Execution Table

Step	Action	Evaluation	Result
1	Define Profile model with OneToOneField to User	Model class created	Profile model ready with user link
2	Create User instance u	User instance created	User object u exists
3	Create Profile instance p linked to u	Profile linked to u	Profile p created with user=u
4	Access p.user	Retrieve linked User	Returns User u
5	Access u.profile	Retrieve linked Profile	Returns Profile p

💡 All steps complete, one-to-one link established and accessible from both sides

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
u (User instance)	None	User object created	User object exists	User object exists
p (Profile instance)	None	None	Profile linked to u	Profile linked to u

Key Moments - 2 Insights

Why can we access the Profile from the User instance using u.profile?

Because OneToOneField creates a reverse relation automatically, so after creating Profile linked to User u, u.profile returns that Profile (see execution_table step 5).

What happens if we try to create two Profile instances linked to the same User?

It will raise an error because OneToOneField enforces only one Profile per User, ensuring one-to-one relationship.

Visual Quiz - 3 Questions

Look at the execution table, what does p.user return at step 4?

A None

B Profile instance p

C User instance u

D Error

💡 Hint

Check execution_table row with Step 4, Action 'Access p.user'

At which step is the Profile instance linked to the User instance?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at execution_table row Step 3 where Profile p is created linked to u

If we try to create another Profile linked to the same User u, what will happen?

A It will raise an error due to one-to-one constraint

B It will create another Profile without issues

C It will overwrite the existing Profile

D It will unlink the first Profile

💡 Hint

Refer to key_moments about one-to-one uniqueness enforcement

Concept Snapshot

OneToOneField links two models so each instance relates to exactly one instance of the other.
Define with OneToOneField in one model pointing to the other.
Creates automatic reverse access (e.g., user.profile).
Enforces uniqueness: one side cannot link to multiple instances.
Useful for extending user profiles or related data.

Full Transcript

This visual execution trace shows how Django's OneToOneField creates a strict one-to-one link between two models. First, a model Profile is defined with a OneToOneField to User. Then a User instance u is created, followed by a Profile instance p linked to u. Accessing p.user returns the linked User u, and accessing u.profile returns the linked Profile p. The one-to-one constraint means only one Profile can link to a User, preventing duplicates. This setup is common for extending user data with related models.