Update mutation pattern in GraphQL - Step-by-Step Execution

Concept Flow - Update mutation pattern

Receive update request

↓

Validate input data

↓

Find record by ID

↓

Apply updates to fields

↓

Save updated record

↓

Return updated record or status

This flow shows how an update mutation receives data, validates it, finds the record, applies changes, saves, and returns the result.

Execution Sample

GraphQL

mutation UpdateUser($id: ID!, $name: String!) {
  updateUser(id: $id, name: $name) {
    id
    name
  }
}

This mutation updates a user's name by their ID and returns the updated user data.

Execution Table

Step	Action	Input/Condition	Result	Next Step
1	Receive mutation request	{id: "123", name: "Alice"}	Request accepted	Validate input
2	Validate input	id present and name is string	Validation passed	Find record by ID
3	Find record	Search user with id=123	User found: {id: "123", name: "Bob"}	Apply updates
4	Apply updates	Set name = "Alice"	User data updated in memory	Save updated record
5	Save updated record	Write changes to database	Database updated successfully	Return updated record
6	Return result	Return updated user data	{id: "123", name: "Alice"}	End

💡 Process ends after returning the updated user data.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
id	undefined	"123"	"123"	"123"
name	undefined	"Bob"	"Alice"	"Alice"
userRecord	undefined	{id: "123", name: "Bob"}	{id: "123", name: "Alice"}	{id: "123", name: "Alice"}

Key Moments - 3 Insights

Why do we validate input before finding the record?

Validating input first (see Step 2 in execution_table) ensures we only search the database with correct and safe data, preventing errors or security issues.

What happens if the user ID is not found?

If the user is not found at Step 3, the mutation would return an error or null, stopping the update process before applying changes.

Why do we return the updated record at the end?

Returning the updated record (Step 6) confirms the update succeeded and shows the current data to the client.

Visual Quiz - 3 Questions

Look at the execution_table, what is the user name after Step 4?

A "Bob"

B "Alice"

C undefined

D "123"

💡 Hint

Check the 'Result' column at Step 4 where the name is updated in memory.

At which step does the mutation save changes to the database?

A Step 2

B Step 3

C Step 5

D Step 6

💡 Hint

Look for the action 'Save updated record' in the execution_table.

If the input validation fails, what happens next?

A The mutation returns an error and stops

B The mutation proceeds to find the record

C The mutation applies updates anyway

D The mutation returns the old record

💡 Hint

Refer to Step 2 where validation is checked before proceeding.

Concept Snapshot

Update Mutation Pattern in GraphQL:
- Receive mutation with ID and fields to update
- Validate input data
- Find record by ID
- Apply updates to fields
- Save changes to database
- Return updated record to client

Full Transcript

This visual execution trace shows how a GraphQL update mutation works step-by-step. First, the mutation receives the update request with an ID and new data. It validates the input to ensure correctness. Then it searches the database for the record by ID. If found, it applies the updates in memory and saves the changes to the database. Finally, it returns the updated record to confirm success. Variables like the user ID and name change during the process, showing how data flows through each step. Key moments include why validation happens first, what if the record is missing, and why returning the updated record matters. The quiz questions help check understanding of these steps.

Practice

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

easy

A. To create new data records

B. To change existing data by specifying an ID and new values

C. To delete data from the database

D. To fetch data without any changes

Solution

1. Step 1: Understand the role of update mutations

   Update mutations modify existing records by identifying them and applying new values.

2. Step 2: Differentiate from other mutation types

   Delete mutations remove data, create mutations add new data, and queries fetch data without changes.

3. Final Answer:

   To change existing data by specifying an ID and new values -> Option B

4. Quick Check:

   Update mutation = change existing data [OK]

Hint: Update mutations modify existing records by ID [OK]

Common Mistakes:

• Confusing update with create or delete mutations
• Thinking update fetches data without changes
• Assuming update creates new records

2. Which of the following is the correct syntax for an update mutation in GraphQL?

easy

A. mutation { updateUser(id: "123", input: {name: "Alice"}) { id name } }

B. mutation { createUser(id: "123", input: {name: "Alice"}) { id name } }

C. query { updateUser(id: "123", input: {name: "Alice"}) { id name } }

D. mutation { deleteUser(id: "123") { id name } }

Solution

1. Step 1: Identify the mutation keyword and operation

   Update mutations use the mutation keyword and specify the update operation with an ID and input object.

2. Step 2: Check the options for correct mutation syntax

   mutation { updateUser(id: "123", input: {name: "Alice"}) { id name } } uses mutation with updateUser and input fields correctly; others use wrong operation or query keyword.

3. Final Answer:

   mutation { updateUser(id: "123", input: {name: "Alice"}) { id name } } -> Option A

4. Quick Check:

   Update mutation syntax = mutation + update operation + input [OK]

Hint: Update mutations use 'mutation' keyword with update operation [OK]

Common Mistakes:

• Using 'query' instead of 'mutation'
• Using create or delete operation instead of update
• Missing input object for new values

3. Given this mutation:

mutation { updatePost(id: "5", input: {title: "New Title"}) { id title content } }

What will be the output if the post with ID 5 exists and has content "Old content"?

medium

A. { "data": { "updatePost": null } }

B. { "data": { "updatePost": { "id": "5", "title": "Old Title", "content": "Old content" } } }

C. { "data": { "updatePost": { "id": "5", "title": "New Title", "content": "Old content" } } }

D. Error: Post with ID 5 not found

Solution

1. Step 1: Understand the mutation effect

   The mutation updates the post with ID 5, changing only the title to "New Title" while keeping other fields unchanged.

2. Step 2: Predict the returned data

   The response includes the updated title and the unchanged content "Old content" along with the ID.

3. Final Answer:

   { "data": { "updatePost": { "id": "5", "title": "New Title", "content": "Old content" } } } -> Option C

4. Quick Check:

   Update mutation returns updated fields plus unchanged fields [OK]

Hint: Update changes specified fields, others remain same [OK]

Common Mistakes:

• Assuming all fields reset or become null
• Expecting error when post exists
• Ignoring unchanged fields in output

4. Identify the error in this update mutation:

mutation { updateUser(input: {name: "Bob"}) { id name } }

medium

A. Missing the ID argument to specify which user to update

B. Input object should be named 'data' instead of 'input'

C. Mutation keyword should be 'query' instead of 'mutation'

D. Cannot update the 'name' field

Solution

1. Step 1: Check required arguments for update mutation

   Update mutations require an ID to identify the record to update.

2. Step 2: Analyze the given mutation

   The mutation lacks the ID argument, so it cannot know which user to update.

3. Final Answer:

   Missing the ID argument to specify which user to update -> Option A

4. Quick Check:

   Update mutation must include ID argument [OK]

Hint: Always include ID to update specific record [OK]

Common Mistakes:

• Omitting the ID argument
• Confusing input object name
• Using 'query' instead of 'mutation'

5. You want to update a user's email and phone number but only if the phone number is provided. Which mutation pattern correctly handles this conditional update?

mutation UpdateUser($id: ID!, $email: String!, $phone: String) {
  updateUser(id: $id, input: {email: $email, phone: $phone}) {
    id
    email
    phone
  }
}

hard

A. Create separate mutations for email and phone updates

B. Always send phone field with empty string if no update needed

C. Use optional input fields and send null for phone if not updating

D. Remove phone field from input object when not updating

Solution

1. Step 1: Understand conditional updates in GraphQL

   To update only provided fields, omit fields not meant to be changed from the input object.

2. Step 2: Analyze options for handling optional phone

   Sending null or empty string may overwrite data; omitting the phone field avoids unintended changes.

3. Final Answer:

   Remove phone field from input object when not updating -> Option D

4. Quick Check:

   Omit fields to keep existing values unchanged [OK]

Hint: Omit fields to avoid overwriting unchanged data [OK]

Common Mistakes:

• Sending null overwrites existing data
• Using empty string instead of omitting field
• Creating unnecessary multiple mutations