Updating documents in Express - Step-by-Step Execution

Concept Flow - Updating documents

Receive HTTP PUT/PATCH request

↓

Extract document ID and update data

↓

Call database update method

↓

Database finds document by ID

↓

Update document

↓

Send success response with updated document

The server receives an update request, finds the document by ID, updates it if found, and sends back the updated document or an error.

Execution Sample

Express

app.patch('/items/:id', async (req, res) => {
  const id = req.params.id;
  const updates = req.body;
  const updatedItem = await Item.findByIdAndUpdate(id, updates, { new: true });
  if (!updatedItem) return res.status(404).send('Not found');
  res.send(updatedItem);
});

This code updates an item by ID with new data and returns the updated item or a 404 error if not found.

Execution Table

Step	Action	Input	Database Result	Response Sent
1	Receive PATCH request	id=123, updates={name:'New'}	N/A	N/A
2	Call findByIdAndUpdate	id=123, updates={name:'New'}	Document found and updated	N/A
3	Check if updatedItem exists	updatedItem != null	True	404 Not Found if false
4	Send updated document	updatedItem with new name	N/A	200 OK with updated document
5	End	N/A	N/A	Request complete

💡 Execution stops after sending the updated document response or 404 error.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
id	undefined	123	123	123	123
updates	undefined	{name:'New'}	{name:'New'}	{name:'New'}	{name:'New'}
updatedItem	undefined	undefined	{_id:123, name:'New'}	{_id:123, name:'New'}	{_id:123, name:'New'}

Key Moments - 2 Insights

Why do we check if updatedItem exists after the update call?

Because if the document with the given ID does not exist, findByIdAndUpdate returns null. Checking updatedItem prevents sending a success response for a non-existent document, as shown in step 3 of the execution_table.

What does the { new: true } option do in findByIdAndUpdate?

It tells the database to return the updated document instead of the original. Without it, updatedItem would be the old document before changes, which can confuse the response as seen in step 2.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of updatedItem after Step 2?

A null

B {_id:123, name:'New'}

C undefined

D An error object

💡 Hint

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

At which step does the server send the 404 Not Found response if the document is missing?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look at the 'Check if updatedItem exists' action in Step 3 of the execution_table.

If the { new: true } option is removed, what changes in updatedItem after Step 2?

A updatedItem will be the original document before update

B updatedItem will be null

C updatedItem will be undefined

D updatedItem will contain an error

💡 Hint

Refer to the key_moments explanation about the { new: true } option.

Concept Snapshot

Updating documents in Express:
- Use PATCH or PUT route with document ID
- Extract ID and update data from request
- Call findByIdAndUpdate(id, updates, { new: true })
- Check if document exists (null means not found)
- Send updated document or 404 error
- { new: true } returns updated document, not original

Full Transcript

This visual execution shows how Express updates documents in a database. First, the server receives a PATCH request with an ID and update data. It calls the database method findByIdAndUpdate with the ID, updates, and the option to return the new document. If the document is found, it updates and returns it. If not found, it sends a 404 error. The variable tracker shows how the ID, updates, and updatedItem change step by step. Key moments clarify why checking for null is important and what the { new: true } option does. The quiz tests understanding of these steps and values.