Bidirectional relationships in GraphQL - Step-by-Step Execution

Concept Flow - Bidirectional relationships

Define Type A

↓

Add field referencing Type B

↓

Define Type B

↓

Add field referencing Type A

↓

Query Type A -> Access Type B

↓

Query Type B -> Access Type A

Bidirectional relationships connect two types so each can access the other through fields.

Execution Sample

GraphQL

type Author {
  id: ID!
  name: String!
  books: [Book!]!
}

type Book {
  id: ID!
  title: String!
  author: Author!
}

Defines Author and Book types where Author has many Books and each Book has one Author.

Execution Table

Step	Action	Evaluation	Result
1	Define Author type with books field referencing Book list	Author.books is a list of Book	Author can access Books
2	Define Book type with author field referencing Author	Book.author is a single Author	Book can access Author
3	Query Author with books field	Fetch Author and their Books	Returns Author data with list of Books
4	Query Book with author field	Fetch Book and its Author	Returns Book data with Author info
5	Access Author from Book.author	Navigate from Book to Author	Author details retrieved
6	Access Books from Author.books	Navigate from Author to Books	List of Books retrieved
7	End of execution	All bidirectional links verified	Execution complete

💡 All bidirectional references established and queries return expected linked data

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
Author.books	undefined	list of Book references	unchanged	unchanged	list of Book references
Book.author	undefined	undefined	Author reference assigned	unchanged	Author reference assigned

Key Moments - 2 Insights

Why do we need to define fields on both types for bidirectional relationships?

Because each type needs a field to access the other, as shown in execution_table rows 1 and 2 where Author.books and Book.author are defined separately.

Can we query one side and get data from the other automatically?

Yes, once both sides are linked, querying Author.books or Book.author returns related data, as shown in rows 3 and 4.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the Book type linked back to Author?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Check the Action column for when Book.author is defined (Step 2).

According to variable_tracker, what is the value of Author.books after step 1?

A list of Book references

B Author reference

C undefined

D empty list

💡 Hint

Look at Author.books row and After 1 column in variable_tracker.

If we remove the author field from Book, what happens to the bidirectional relationship?

A Author can still access Books

B Book can no longer access Author

C Both sides lose access

D No effect on queries

💡 Hint

Refer to key_moments about needing fields on both types for bidirectional access.

Concept Snapshot

Bidirectional relationships connect two types with fields referencing each other.
Define a field on Type A pointing to Type B and vice versa.
This allows queries from either side to access related data.
Example: Author has books field (list of Book), Book has author field (single Author).
Both fields must be defined for full bidirectional access.

Full Transcript

Bidirectional relationships in GraphQL mean two types reference each other through fields. For example, an Author type has a books field that lists Book types, and each Book type has an author field pointing back to Author. This setup lets you query from Author to get their Books, or from Book to get its Author. The execution flow starts by defining Author with a books field, then Book with an author field. Queries then fetch linked data from either side. Variables track these references as they are assigned. Key points include needing fields on both types for full bidirectional access and that queries return linked data once both sides are connected. The visual quiz tests understanding of when links are defined and what happens if one side is missing.

Practice

1. What is the main purpose of bidirectional relationships in GraphQL schemas?

easy

A. To connect two types so you can query related data from both sides

B. To make the schema run faster by caching data

C. To encrypt data between client and server

D. To limit the number of queries a client can make

Solution

1. Step 1: Understand what bidirectional relationships do

   They link two types so you can access related data from either type easily.

2. Step 2: Compare options to this purpose

   Only To connect two types so you can query related data from both sides describes this linking and querying from both sides.

3. Final Answer:

   To connect two types so you can query related data from both sides -> Option A

4. Quick Check:

   Bidirectional relationships = connect types both ways [OK]

Hint: Think: Can I get related data from both types? That's bidirectional [OK]

Common Mistakes:

• Confusing bidirectional with performance optimization
• Thinking it encrypts data
• Assuming it limits queries

2. Which of the following is the correct way to define a bidirectional relationship between Author and Book types in GraphQL SDL?

easy

A. type Author { books: Book } type Book { author: [Author] }

B. type Author { books: [Author] } type Book { author: [Book] }

C. type Author { books: Book } type Book { author: Book }

D. type Author { books: [Book] } type Book { author: Author }

Solution

1. Step 1: Check the relationship types

   An author can have many books, so books should be a list of Book. Each book has one author, so author is a single Author.

2. Step 2: Match this to options

   Only type Author { books: [Book] } type Book { author: Author } correctly uses [Book] for books and Author for author.

3. Final Answer:

   type Author { books: [Book] } type Book { author: Author } -> Option D

4. Quick Check:

   List on many side, single on one side = type Author { books: [Book] } type Book { author: Author } [OK]

Hint: Many side uses list [], one side uses single type [OK]

Common Mistakes:

• Using single type where list is needed
• Swapping list and single types
• Using wrong type names

3. Given the following GraphQL schema snippet:

type User { posts: [Post] } type Post { author: User }

What will be the result of this query?

{ user { posts { author { id } } } }

medium

A. { "data": { "user": { "posts": [{ "author": { "id": "..." } }, ...] } } }

B. Syntax error due to missing fields

C. { "data": { "user": { "posts": null } } }

D. Runtime error because of circular reference

Solution

1. Step 1: Understand the schema and query

   User has posts, each post has an author. Query asks for user's posts and each post's author id.

2. Step 2: Predict the query result

   Since fields exist and are linked bidirectionally, the query returns posts with author ids nested properly.

3. Final Answer:

   { "data": { "user": { "posts": [{ "author": { "id": "..." } }, ...] } } } -> Option A

4. Quick Check:

   Bidirectional query returns nested data correctly [OK]

Hint: Bidirectional means nested data is accessible both ways [OK]

Common Mistakes:

• Thinking circular references cause runtime errors
• Assuming missing fields cause syntax errors
• Expecting null when data exists

4. You have this GraphQL schema:

type Category { products: [Product] } type Product { category: Category }

But your query for category { products { category { id } }} returns null for category inside products. What is the likely cause?

medium

A. The products field should not be a list

B. GraphQL does not support nested bidirectional queries

C. The category field in Product is not properly resolved or linked

D. The query syntax is invalid

Solution

1. Step 1: Analyze the schema and query

   Schema defines bidirectional links. Query asks for category's products and each product's category id.

2. Step 2: Identify why nested category is null

   If nested category is null, likely the resolver for category in Product is missing or incorrect.

3. Final Answer:

   The category field in Product is not properly resolved or linked -> Option C

4. Quick Check:

   Missing resolver causes null nested fields [OK]

Hint: Null nested fields often mean missing resolver functions [OK]

Common Mistakes:

• Assuming GraphQL can't do nested bidirectional queries
• Thinking list types cause nulls
• Blaming query syntax without error

5. You want to model a bidirectional relationship between Employee and Manager where each employee has one manager, and each manager can have many employees. Which schema correctly models this with bidirectional fields?

hard

A. type Employee { manager: Employee } type Manager { employees: [Manager] }

B. type Employee { manager: Manager } type Manager { employees: [Employee] }

C. type Employee { manager: Manager } type Manager { employees: Employee }

D. type Employee { manager: [Manager] } type Manager { employees: Employee }

Solution

1. Step 1: Understand the relationship

   Each employee has one manager (single), each manager has many employees (list).

2. Step 2: Match schema fields to this

   Employee's manager is a single Manager. Manager's employees is a list of Employee.

3. Final Answer:

   type Employee { manager: Manager } type Manager { employees: [Employee] } -> Option B

4. Quick Check:

   One-to-many bidirectional = single on one side, list on other [OK]

Hint: One side single type, other side list type for one-to-many [OK]

Common Mistakes:

• Swapping list and single types
• Using wrong types for fields
• Confusing employee and manager roles