Many-to-many relationships in GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a many-to-many relationship in databases?

A many-to-many relationship happens when multiple records in one table relate to multiple records in another table. For example, students can enroll in many courses, and courses can have many students.

beginner

How do many-to-many relationships get represented in a database?

They are represented using a join table (also called a junction or linking table) that holds foreign keys from both related tables. This table connects the records from both sides.

intermediate

In GraphQL, how can you model a many-to-many relationship between two types?

You create two types and include a list field in each type that references the other type. The actual linking is handled in the database, often with a join table.

beginner

Why is a join table necessary for many-to-many relationships?

Because relational databases cannot directly link many records to many others without an intermediate table to store each pair of related records.

intermediate

Give a simple GraphQL schema example showing many-to-many between Authors and Books.

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

What does a join table in a many-to-many relationship typically contain?

A Foreign keys from both related tables

B Only primary keys of one table

C Data unrelated to the relationship

D Only one foreign key

A join table contains foreign keys from both tables to link their records.

In GraphQL, how do you represent a many-to-many relationship between two types?

A By adding a list of the other type in each type

B By using scalar fields only

C By creating only one type

D By avoiding lists in the schema

You add a list field of the related type in each type to represent many-to-many.

Why can't relational databases directly store many-to-many relationships without a join table?

A Because tables can only have one primary key

B Because many-to-many needs an intermediate table to link records

C Because databases do not support relationships

D Because foreign keys are not allowed

Many-to-many relationships require an intermediate join table to link records.

Which of these is an example of a many-to-many relationship?

A One country has many cities

B Each employee has one manager

C Each book has one author

D One student enrolls in many courses, and each course has many students

Students and courses relate many-to-many because both sides can have multiple connections.

In a GraphQL schema, what type of field would you use to show multiple related records?

A A scalar field, e.g., String

B A single ID field

C A list field, e.g., [TypeName!]

D A Boolean field

Lists in GraphQL represent multiple related records.

Explain how many-to-many relationships work and how they are represented in databases and GraphQL.

Think about students and courses as an example.

Describe why a join table is necessary and how it connects two tables in a many-to-many relationship.

Imagine a table that stores pairs of IDs.

Practice

1. In GraphQL, how do you represent a many-to-many relationship between two types, for example, Author and Book?

easy

A. By having a list of Book in Author and a list of Author in Book

B. By having a single field of Book in Author only

C. By using scalar fields only, no lists

D. By embedding Author inside Book as a string

Solution

1. Step 1: Understand many-to-many relationship in GraphQL

   Many-to-many means each Author can have many Books and each Book can have many Authors.

2. Step 2: Represent with lists on both types

   To model this, both Author and Book types should have a list field referencing the other type.

3. Final Answer:

   By having a list of Book in Author and a list of Author in Book -> Option A

4. Quick Check:

   Many-to-many = lists on both sides [OK]

Hint: Use lists on both types to link many items [OK]

Common Mistakes:

• Using a single object instead of a list
• Not linking both types with lists
• Using scalar fields instead of object references

2. Which of the following is the correct GraphQL schema snippet to define a many-to-many relationship between Student and Course?

easy

A. type Student { course: Course } type Course { student: Student }

B. type Student { courses: Course } type Course { students: Student }

C. type Student { courses: String } type Course { students: String }

D. type Student { courses: [Course!]! } type Course { students: [Student!]! }

Solution

1. Step 1: Check list syntax for many-to-many

   Many-to-many requires lists, so fields must be lists like [Course!]! and [Student!]!.

2. Step 2: Validate non-null and list usage

   type Student { courses: [Course!]! } type Course { students: [Student!]! } correctly uses non-null lists of non-null items, which is best practice.

3. Final Answer:

   type Student { courses: [Course!]! } type Course { students: [Student!]! } -> Option D

4. Quick Check:

   Lists with non-null = correct schema [OK]

Hint: Use square brackets for lists in GraphQL schema [OK]

Common Mistakes:

• Missing square brackets for lists
• Using singular fields instead of lists
• Using scalar types instead of object types

3. Given this GraphQL query on a many-to-many schema:

query { students { name courses { title } } }

What will the result include?

medium

A. A list of students with their names and a list of their enrolled courses' titles

B. Only student names without any course information

C. Only course titles without student names

D. An error because nested queries are not allowed

Solution

1. Step 1: Understand the query structure

   The query requests students with their name and nested courses with title.

2. Step 2: Interpret many-to-many data fetching

   Since courses is a list on Student, the result includes each student's name and their list of course titles.

3. Final Answer:

   A list of students with their names and a list of their enrolled courses' titles -> Option A

4. Quick Check:

   Nested lists fetch related data [OK]

Hint: Nested fields fetch linked many-to-many data [OK]

Common Mistakes:

• Expecting only flat data without nested lists
• Thinking nested queries cause errors
• Ignoring the many-to-many list structure

4. You wrote this GraphQL schema snippet:

type User { groups: Group } type Group { users: User }

Why does this cause problems in representing many-to-many relationships?

medium

A. Because the field names are incorrect

B. Because groups and users are not lists, so only one group or user can be linked

C. Because GraphQL does not allow circular references

D. Because the types are missing scalar fields

Solution

1. Step 1: Check field types for many-to-many

   Many-to-many requires lists on both sides, but here groups and users are single objects, not lists.

2. Step 2: Understand impact on data modeling

   This means each User can link to only one Group and vice versa, not many, so it breaks many-to-many.

3. Final Answer:

   Because groups and users are not lists, so only one group or user can be linked -> Option B

4. Quick Check:

   Lists needed for many-to-many [OK]

Hint: Use lists, not single objects, for many-to-many fields [OK]

Common Mistakes:

• Using single object fields instead of lists
• Assuming circular references cause errors
• Ignoring the need for lists in many-to-many

5. You have a many-to-many relationship between Artist and Album. You want to fetch all artists with their albums, but only include albums released after 2020. Which GraphQL query correctly applies this filter?

hard

A. query { artists { name albums { title releaseYear } where: { releaseYear > 2020 } } }

B. query { artists { name albums { title releaseYear filter: { releaseYear > 2020 } } } }

C. query { artists { name albums(where: { releaseYear_gt: 2020 }) { title releaseYear } } }

D. query { artists { name albums { title releaseYear } } filter: { releaseYear > 2020 } }

Solution

1. Step 1: Identify correct filter syntax in GraphQL

   GraphQL commonly uses arguments like where with conditions such as releaseYear_gt: 2020 to filter nested lists.

2. Step 2: Check query structure for filtering nested albums

   query { artists { name albums(where: { releaseYear_gt: 2020 }) { title releaseYear } } }

   correctly places the where argument inside the albums field to filter albums after 2020.

3. Final Answer:

   query { artists { name albums(where: { releaseYear_gt: 2020 }) { title releaseYear } } } -> Option C

4. Quick Check:

   Use where argument inside nested field [OK]

Hint: Apply filters as arguments inside nested fields [OK]

Common Mistakes:

• Placing filters outside nested fields
• Using invalid filter syntax
• Not filtering at the nested list level