CRUD operations in Flask - Step-by-Step Execution

Concept Flow - CRUD operations

Client sends HTTP request

↓

Flask route matches URL

↓

Identify CRUD operation

↓

Process data

↓

Send HTTP response

This flow shows how Flask handles HTTP requests for CRUD: create, read, update, and delete data, then sends back a response.

Execution Sample

Flask

from flask import Flask, request, jsonify
app = Flask(__name__)

items = []

@app.route('/items', methods=['POST'])
def create_item():
    data = request.json
    items.append(data)
    return jsonify(data), 201

This code adds a new item to a list when a POST request is sent to /items.

Execution Table

Step	HTTP Method	Route	Action	Data State	Response
1	POST	/items	Receive JSON data {'name': 'apple'}	items = []	Waiting
2	POST	/items	Append {'name': 'apple'} to items	items = [{'name': 'apple'}]	Waiting
3	POST	/items	Return JSON {'name': 'apple'} with status 201	items = [{'name': 'apple'}]	Response sent: 201 Created
4	GET	/items	Return all items	items = [{'name': 'apple'}]	Response sent: [{'name': 'apple'}]
5	PUT	/items/0	Update item at index 0 with {'name': 'banana'}	items = [{'name': 'banana'}]	Response sent: {'name': 'banana'}
6	DELETE	/items/0	Remove item at index 0	items = []	Response sent: 204 No Content
7	-	-	No more requests	items = []	End of execution

💡 No more HTTP requests to process, CRUD cycle complete.

Variable Tracker

Variable	Start	After Step 2	After Step 5	After Step 6	Final
items	[]	[{'name': 'apple'}]	[{'name': 'banana'}]	[]	[]

Key Moments - 3 Insights

Why does the list 'items' change after a POST request?

Because in step 2, the POST request adds the new data to the 'items' list, updating its state as shown in the execution_table.

What happens if we try to DELETE an item that does not exist?

The code would likely raise an error or return a 404 response, but in this trace, deletion only happens when the item exists (step 6).

Why does the PUT request update the item instead of adding a new one?

Because the PUT method targets a specific item index (step 5), replacing the existing data rather than appending.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'items' after step 2?

A []

B [{'name': 'apple'}]

C [{'name': 'banana'}]

D [{'name': 'apple'}, {'name': 'banana'}]

💡 Hint

Check the 'Data State' column in row for step 2.

At which step does the 'items' list become empty again?

A Step 3

B Step 5

C Step 6

D Step 4

💡 Hint

Look at the 'Data State' column and find when 'items' is [].

If the POST request sent {'name': 'orange'} instead of {'name': 'apple'}, what would be the 'items' state after step 2?

A [{'name': 'orange'}]

B [{'name': 'apple'}]

C []

D [{'name': 'banana'}]

💡 Hint

Step 2 shows the list after appending the POST data.

Concept Snapshot

CRUD operations in Flask:
- Create: POST /items adds data
- Read: GET /items returns data
- Update: PUT /items/<id> modifies data
- Delete: DELETE /items/<id> removes data
Each route handles one operation and updates the data store accordingly.

Full Transcript

This visual trace shows how Flask handles CRUD operations step-by-step. When a client sends a POST request to /items with JSON data, Flask adds that data to the items list and returns it with status 201. A GET request returns all items. A PUT request updates an item at a specific index, and DELETE removes it. The variable tracker shows how the items list changes after each operation. Key moments clarify why the list changes after POST, how PUT updates instead of adds, and what happens on deletion. The quiz tests understanding of the data state after each step. This helps beginners see how Flask routes map to CRUD actions and how data changes over time.