Why mutations modify data in GraphQL - Quick Recap

Recall & Review

beginner

What is a mutation in GraphQL?

A mutation is a special type of GraphQL operation used to change or modify data on the server, such as creating, updating, or deleting records.

beginner

Why do mutations modify data instead of just fetching it?

Mutations are designed to change data because they represent actions that alter the state of the server, unlike queries which only read data without changing it.

beginner

How does a mutation differ from a query in GraphQL?

A query only retrieves data without changing it, while a mutation performs operations that modify data, such as adding or updating records.

intermediate

What happens on the server when a mutation is executed?

The server processes the mutation by applying the requested changes to the database or data source, then returns the updated data or confirmation.

intermediate

Can mutations return data? Why is this useful?

Yes, mutations can return data such as the updated or newly created records. This helps clients immediately see the result of their changes without making a separate query.

What is the primary purpose of a mutation in GraphQL?

A To delete the GraphQL schema

B To fetch data without changes

C To modify data on the server

D To create a new query

Mutations are specifically designed to modify data on the server, unlike queries which only fetch data.

Which GraphQL operation should you use to update a user's email address?

A Query

B Subscription

C Fragment

D Mutation

Updating data requires a mutation because it changes the server's data.

After a mutation modifies data, what can it return to the client?

A The updated or created data

B Only error messages

C Nothing, mutations never return data

D The entire database

Mutations can return the updated or newly created data so clients can see the result immediately.

Which of the following is NOT a typical use of a mutation?

A Creating a new user

B Fetching a list of products

C Deleting a comment

D Updating a profile picture

Fetching data is done with queries, not mutations.

Why are mutations important in client-server communication?

A They allow clients to change data on the server

B They speed up data fetching

C They encrypt data automatically

D They create new GraphQL schemas

Mutations enable clients to send changes to the server, modifying data as needed.

Explain in your own words why mutations are used to modify data in GraphQL.

Think about the difference between reading and writing data.

Describe what happens on the server when a mutation is executed.

Focus on the server's role in handling data changes.

Practice

1. What is the main purpose of a mutation in GraphQL?

easy

A. To modify data by adding, updating, or deleting it

B. To only fetch data without changes

C. To define the schema structure

D. To create a new query type

Solution

1. Step 1: Understand the role of mutations

   Mutations are designed to change data, unlike queries which only fetch data.

2. Step 2: Identify the correct purpose

   Since mutations add, update, or delete data, their main purpose is to modify data.

3. Final Answer:

   To modify data by adding, updating, or deleting it -> Option A

4. Quick Check:

   Mutation = Modify data [OK]

Hint: Mutations always change data, queries only read data [OK]

Common Mistakes:

• Confusing mutations with queries
• Thinking mutations only fetch data
• Believing mutations define schema only

2. Which of the following is the correct way to start a mutation operation in GraphQL?

easy

A. modify { updateUser(id: 1) { name } }

B. query { updateUser(id: 1) { name } }

C. update { updateUser(id: 1) { name } }

D. mutation { updateUser(id: 1) { name } }

Solution

1. Step 1: Identify the keyword for mutations

   GraphQL uses the keyword mutation to start mutation operations.

2. Step 2: Check the options

   Only mutation { updateUser(id: 1) { name } } uses the correct mutation keyword to start the operation.

3. Final Answer:

   mutation { updateUser(id: 1) { name } } -> Option D

4. Quick Check:

   Mutation keyword = mutation [OK]

Hint: Mutations always start with the 'mutation' keyword [OK]

Common Mistakes:

• Using 'query' instead of 'mutation'
• Using non-existent keywords like 'update' or 'modify'
• Omitting the mutation keyword

3. Given the mutation below, what will be the result if the user with id 2 exists?

mutation {
  updateUser(id: 2, input: {name: "Alice"}) {
    id
    name
  }
}

medium

A. Syntax error due to missing input type

B. { "data": { "updateUser": null } }

C. { "data": { "updateUser": { "id": 2, "name": "Alice" } } }

D. No change, returns old user data

Solution

1. Step 1: Understand mutation behavior

   The mutation updates user with id 2, changing the name to "Alice".

2. Step 2: Predict the returned data

   The mutation returns the updated user data with id and new name.

3. Final Answer:

   { "data": { "updateUser": { "id": 2, "name": "Alice" } } } -> Option C

4. Quick Check:

   Mutation updates and returns new data [OK]

Hint: Mutations return updated data if successful [OK]

Common Mistakes:

• Assuming mutation returns null on success
• Thinking mutation causes syntax error here
• Believing mutation returns old data without changes

4. Identify the error in this mutation:

mutation {
  addUser(name: "Bob")
  {
    id
    name
  }
}

medium

A. Mutation keyword is incorrect

B. Missing input argument object for addUser

C. Curly braces are misplaced

D. No error, mutation is correct

Solution

1. Step 1: Check mutation input format

   Mutations usually require input as an object, e.g., addUser(input: {name: "Bob"}).

2. Step 2: Identify missing input argument

   The mutation lacks the input argument object, causing an error.

3. Final Answer:

   Missing input argument object for addUser -> Option B

4. Quick Check:

   Input argument missing = error [OK]

Hint: Mutations need input objects for data changes [OK]

Common Mistakes:

• Forgetting to wrap inputs in an object
• Misplacing curly braces
• Confusing mutation keyword

5. You want to delete a user and then immediately fetch the updated user list in one mutation operation. Which approach correctly uses mutations to achieve this?

hard

A. Use a single mutation with two fields: deleteUser and users to delete and fetch updated list

B. Use a query to delete the user and a mutation to fetch the list

C. Use two separate mutations, one for deleting and one for fetching users

D. Use a mutation to delete the user and a query to fetch the updated list separately

Solution

1. Step 1: Understand mutation capabilities

   GraphQL mutations can include multiple fields to perform several operations in one request.

2. Step 2: Identify correct approach

   Using a single mutation with deleteUser and users fields allows deleting and fetching updated data atomically.

3. Final Answer:

   Use a single mutation with two fields: deleteUser and users to delete and fetch updated list -> Option A

4. Quick Check:

   Single mutation can do multiple related operations [OK]

Hint: Combine delete and fetch in one mutation for atomic update [OK]

Common Mistakes:

• Trying to delete with a query
• Splitting operations into separate requests unnecessarily
• Using mutation only for delete without fetching updated data