CRUD operations with Sequelize in Express - Step-by-Step Execution

Concept Flow - CRUD operations with Sequelize

Start

↓

Create Model Instance

↓

Read Data

↓

Update Data

↓

Delete Data

↓

End

This flow shows the four main steps of CRUD with Sequelize: create, read, update, and delete data in the database.

Execution Sample

Express

const user = await User.create({ name: 'Ana' });
const foundUser = await User.findByPk(user.id);
await foundUser.update({ name: 'Anna' });
await foundUser.destroy();

This code creates a user, reads it by ID, updates the name, then deletes the user.

Execution Table

Step	Action	Input	Sequelize Method	Result	Database State
1	Create user	{ name: 'Ana' }	User.create	User instance with id=1	User table has 1 record: { id:1, name:'Ana' }
2	Read user by ID	id=1	User.findByPk	User instance with id=1, name='Ana'	No change
3	Update user name	{ name: 'Anna' }	foundUser.update	User instance updated to name='Anna'	User table record updated: { id:1, name:'Anna' }
4	Delete user	none	foundUser.destroy	User instance deleted	User table is empty
5	Exit	No more actions	N/A	End of CRUD operations	Final database state: empty user table

💡 All CRUD steps completed; user record created, read, updated, then deleted.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
user	undefined	{ id:1, name:'Ana' }	{ id:1, name:'Ana' }	{ id:1, name:'Anna' }	{ id:1, name:'Anna' } (deleted)
foundUser	undefined	undefined	{ id:1, name:'Ana' }	{ id:1, name:'Anna' }	{ id:1, name:'Anna' } (deleted)

Key Moments - 3 Insights

Why does the 'user' variable still hold data after creation even after deletion?

After creation, 'user' holds the new instance returned by User.create (see Step 1). After deletion (Step 4), the instance is removed from the database, so 'user' no longer represents a valid record.

Why do we use 'findByPk' to read the user instead of reusing the 'user' variable?

Using 'findByPk' (Step 2) simulates fetching fresh data from the database, ensuring we read the current state, not just the in-memory object.

What happens if we try to update a user after deletion?

After deletion (Step 4), the user instance no longer exists in the database, so calling update would fail or throw an error because the record is gone.

Visual Quiz - 3 Questions

Look at the execution table, what is the database state after Step 3?

A User table has 1 record with name 'Anna'

B User table is empty

C User table has 1 record with name 'Ana'

D User table has 2 records

💡 Hint

Check the 'Database State' column at Step 3 in the execution table.

At which step does the user instance get deleted from the database?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look for the 'Delete user' action in the execution table.

If we skip Step 2 (reading the user), what impact does it have on the variable 'foundUser'?

A 'foundUser' holds the created user instance

B 'foundUser' remains undefined

C 'foundUser' holds the updated user instance

D 'foundUser' holds the deleted user instance

💡 Hint

Refer to the variable_tracker for 'foundUser' after Step 2.

Concept Snapshot

CRUD with Sequelize:
- Create: Model.create({data}) adds a record.
- Read: Model.findByPk(id) fetches by primary key.
- Update: instance.update({data}) changes fields.
- Delete: instance.destroy() removes record.
Each step changes database state accordingly.

Full Transcript

This visual execution shows how to perform CRUD operations using Sequelize in Express. First, we create a user with User.create, which adds a record to the database and returns the instance. Next, we read the user by primary key using User.findByPk to get fresh data. Then, we update the user's name with instance.update, changing the database record. Finally, we delete the user with instance.destroy, removing the record. The variable tracker shows how the user instance changes through these steps. Key moments clarify why reading fresh data matters and what happens after deletion. The quiz tests understanding of database state and variable values at each step.