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

Concept Flow - Delete mutation pattern

Client sends Delete Mutation Request

↓

Server receives mutation with ID

↓

Server checks if record exists

↓

Delete record

↓

Return success response

The client sends a delete request with an ID, the server checks if the record exists, deletes it if found, and returns success or error.

Execution Sample

GraphQL

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

This mutation requests to delete a user with ID '123' and returns the deleted user's id and name.

Execution Table

Step	Action	Input	Check	Result	Output
1	Receive mutation	id = '123'	N/A	Mutation accepted	N/A
2	Check record existence	id = '123'	Record found?	Yes	N/A
3	Delete record	id = '123'	N/A	Record deleted	N/A
4	Return response	Deleted user data	N/A	Success	{ id: "123", name: "Alice" }
5	End	N/A	N/A	Mutation complete	N/A

💡 Mutation ends after returning success response with deleted user data.

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
id	undefined	"123"	"123"	"123"
recordExists	undefined	true	true	true
deletedRecord	undefined	undefined	{ id: "123", name: "Alice" }	{ id: "123", name: "Alice" }
response	undefined	undefined	undefined	{ id: "123", name: "Alice" }

Key Moments - 2 Insights

What happens if the record with the given ID does not exist?

If the record does not exist (Step 2 check is No), the server returns an error response instead of deleting, stopping the mutation early.

Why does the mutation return the deleted record's data?

Returning the deleted record's data confirms what was deleted and helps the client update its state accordingly, as shown in Step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the result of the record existence check at Step 2?

A Yes

B No

C Error

D Undefined

💡 Hint

Check the 'Result' column in Step 2 of the execution_table.

At which step is the record actually deleted?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'Action' column to find when deletion happens.

If the record did not exist, how would the execution table change?

A Step 3 would delete a record anyway

B Step 4 would return deleted user data

C Step 2 result would be 'No' and mutation would return error

D Mutation would continue normally

💡 Hint

Refer to key_moments about what happens when record is missing.

Concept Snapshot

Delete Mutation Pattern in GraphQL:
- Client sends mutation with record ID.
- Server checks if record exists.
- If yes, deletes record and returns deleted data.
- If no, returns error.
- Helps client confirm deletion and update UI.

Full Transcript

In the Delete mutation pattern, the client sends a mutation request with the ID of the record to delete. The server receives this request and checks if the record exists. If the record is found, the server deletes it and returns the deleted record's data as confirmation. If the record does not exist, the server returns an error. This pattern ensures the client knows exactly what was deleted or if the deletion failed. The execution table shows each step: receiving the mutation, checking existence, deleting, and returning the response. Variables like the record ID, existence flag, and deleted record data change as the mutation progresses. Understanding these steps helps beginners see how delete mutations work in GraphQL.

Practice

1.

What is the main purpose of a delete mutation in GraphQL?

easy

A. To update existing data in the database

B. To add new data to the database

C. To remove data from the database using an identifier

D. To fetch data without modifying it

Solution

1. Step 1: Understand the role of delete mutations

   Delete mutations are designed to remove data entries, usually by specifying an ID or unique key.

2. Step 2: Compare with other mutation types

   Add mutations create data, update mutations modify data, and queries fetch data without changes.

3. Final Answer:

   To remove data from the database using an identifier -> Option C

4. Quick Check:

   Delete mutation = remove data [OK]

Hint: Delete mutations always remove data by ID [OK]

Common Mistakes:

• Confusing delete with add or update mutations
• Thinking delete fetches data
• Assuming delete mutations do not require an identifier

2.

Which of the following is the correct syntax for a GraphQL delete mutation to remove a user by ID?

mutation {
  deleteUser(id: "123") {
    success
    message
  }
}

easy

A. mutation { deleteUser(id: "123") { success message } }

B. mutation { deleteUser { id: "123" success message } }

C. mutation { deleteUser(id: 123) { success message } }

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

Solution

1. Step 1: Check argument placement and syntax

   The ID must be passed as an argument inside parentheses with quotes for string: id: "123".

2. Step 2: Verify the selection set braces

   The fields to return (success, message) must be inside braces after the mutation call.

3. Final Answer:

   mutation { deleteUser(id: "123") { success message } } -> Option A

4. Quick Check:

   Correct syntax = mutation { deleteUser(id: "123") { success message } } [OK]

Hint: Arguments go inside parentheses, fields inside braces [OK]

Common Mistakes:

• Passing id without quotes for string
• Placing fields outside braces
• Misplacing argument inside selection set

3.

Given the following delete mutation and response, what is the value of success?

mutation {
  deletePost(id: "abc") {
    success
    message
  }
}

Response:

{
  "data": {
    "deletePost": {
      "success": true,
      "message": "Post deleted successfully"
    }
  }
}

medium

A. false

B. true

C. null

D. undefined

Solution

1. Step 1: Read the mutation response carefully

   The response shows the success field inside deletePost as true.

2. Step 2: Understand the meaning of success

   A true value means the deletion was successful.

3. Final Answer:

   true -> Option B

4. Quick Check:

   Response success = true [OK]

Hint: Check response JSON for success field value [OK]

Common Mistakes:

• Confusing success with message content
• Assuming success is false without checking response
• Ignoring JSON structure

4.

Identify the error in this delete mutation:

mutation {
  deleteComment(commentId: 456) {
    success
    message
  }
}

medium

A. Missing quotes around the commentId value

B. Missing selection set braces

C. Incorrect mutation keyword

D. Using wrong field names in response

Solution

1. Step 1: Check argument data type

   The commentId is likely a string and should be enclosed in quotes: "456".

2. Step 2: Verify mutation syntax

   The mutation keyword and selection set braces are correct; field names are valid.

3. Final Answer:

   Missing quotes around the commentId value -> Option A

4. Quick Check:

   String IDs need quotes [OK]

Hint: String IDs must be in quotes in mutations [OK]

Common Mistakes:

• Passing string IDs without quotes
• Omitting braces around fields
• Using wrong mutation keyword

5.

You want to delete multiple users by their IDs in one mutation call. Which approach correctly applies the delete mutation pattern?

Options:

1. mutation { deleteUsers(ids: ["1", "2", "3"]) { success message } }
2. mutation { deleteUser(id: "1") { success message } deleteUser(id: "2") { success message } }
3. mutation { deleteUser(id: "1") { success message } }
4. mutation { deleteUsers(ids: "1,2,3") { success message } }

hard

A. Call deleteUser mutation multiple times in one request

B. Pass IDs as a comma-separated string in deleteUsers(ids: "1,2,3")

C. Delete only one user at a time with deleteUser(id: "1")

D. Use a single mutation with an array of IDs: deleteUsers(ids: ["1", "2", "3"])

Solution

1. Step 1: Understand batch deletion

   To delete multiple users at once, the mutation must accept an array of IDs.

2. Step 2: Evaluate options

   Use a single mutation with an array of IDs: deleteUsers(ids: ["1", "2", "3"]) correctly passes an array of strings. Call deleteUser mutation multiple times in one request tries multiple mutations in one call, which is invalid syntax. Delete only one user at a time with deleteUser(id: "1") deletes only one user. Pass IDs as a comma-separated string in deleteUsers(ids: "1,2,3") passes a string instead of an array.

3. Final Answer:

   Use a single mutation with an array of IDs: deleteUsers(ids: ["1", "2", "3"]) -> Option D

4. Quick Check:

   Batch delete uses array of IDs [OK]

Hint: Batch deletes use array arguments, not comma strings [OK]

Common Mistakes:

• Trying multiple mutations in one call
• Passing IDs as comma string instead of array
• Assuming single delete mutation handles multiple IDs