ORM concept (Sequelize, Prisma overview) in Node.js - Step-by-Step Execution

Concept Flow - ORM concept (Sequelize, Prisma overview)

Define Models

↓

Connect to Database

↓

Perform CRUD Operations

↓

ORM Translates to SQL

↓

Database Executes SQL

↓

Return Results to App

This flow shows how ORM tools like Sequelize or Prisma let you define data models, connect to a database, perform operations, and get results without writing raw SQL.

Execution Sample

Node.js

const user = await prisma.user.create({
  data: { name: 'Alice', email: '[e-mail]' }
});
console.log(user);

This code creates a new user record in the database using Prisma ORM and prints the created user object.

Execution Table

Step	Action	ORM Method	SQL Generated	Result
1	Call prisma.user.create	create({ data: {...} })	INSERT INTO users (name, email) VALUES ('Alice', '[e-mail]');	Pending promise
2	Database executes SQL	N/A	N/A	New user record inserted
3	Prisma returns created user	N/A	N/A	{ id: 1, name: 'Alice', email: '[e-mail]' }
4	Console logs user	N/A	N/A	Prints user object to console

💡 User created and returned, operation complete

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
user	undefined	Promise pending	{ id: 1, name: 'Alice', email: '[e-mail]' }	{ id: 1, name: 'Alice', email: '[e-mail]' }

Key Moments - 2 Insights

Why don't we write SQL directly when using ORM?

ORM methods like prisma.user.create generate SQL behind the scenes (see execution_table step 1). This lets you work with JavaScript objects instead of raw SQL strings.

What does the ORM return after creating a record?

After the database inserts the record (step 2), ORM returns the created object with its new ID (step 3), so you can use it immediately.

Visual Quiz - 3 Questions

Look at the execution table, what SQL command does prisma.user.create generate?

A UPDATE users SET name='Alice' WHERE id=1;

B SELECT * FROM users;

C INSERT INTO users (name, email) VALUES ('Alice', '[e-mail]');

D DELETE FROM users WHERE id=1;

💡 Hint

Check the 'SQL Generated' column in step 1 of the execution table.

At which step does the ORM return the created user object?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Result' column to see when the user object is returned.

If the database failed to insert the user, what would change in the execution table?

A Step 1 would not generate SQL

B Step 2 would show an error instead of success

C Step 4 would print the user object

D Step 3 would return a different user

💡 Hint

Database execution happens at step 2; failure would be noted there.

Concept Snapshot

ORM lets you work with database data using code objects.
Define models, then use ORM methods for create, read, update, delete.
ORM converts these calls into SQL behind the scenes.
You get back JavaScript objects representing your data.
Sequelize and Prisma are popular Node.js ORMs.
They simplify database work without writing SQL directly.

Full Transcript

ORM stands for Object-Relational Mapping. It helps developers work with databases using code objects instead of SQL. In Node.js, tools like Sequelize and Prisma let you define data models and perform operations like creating or reading records with simple method calls. For example, calling prisma.user.create with data creates a new user in the database. Behind the scenes, the ORM generates SQL commands like INSERT statements and sends them to the database. The database executes the SQL and returns results, which the ORM converts back into JavaScript objects. This process saves time and reduces errors by avoiding manual SQL writing. The execution table shows each step: calling the ORM method, generating SQL, database execution, and returning the created object. Variables like 'user' start undefined, then hold a promise, and finally the created user object. Beginners often wonder why SQL isn't written directly; the ORM handles that automatically. They also ask what the ORM returns after creation; it returns the full object including new IDs. Understanding these steps helps you use ORMs confidently to manage database data in your Node.js apps.

Practice

1. What is the main purpose of an ORM like Sequelize or Prisma in Node.js?

easy

A. To simplify database operations by using JavaScript code instead of raw SQL

B. To replace Node.js as a runtime environment

C. To create user interfaces for web applications

D. To manage server hardware resources

Solution

1. Step 1: Understand what ORM stands for

   ORM means Object-Relational Mapping, which helps translate code into database queries.

2. Step 2: Identify ORM's role in Node.js

   Sequelize and Prisma let developers write JavaScript code to interact with databases instead of writing SQL directly.

3. Final Answer:

   To simplify database operations by using JavaScript code instead of raw SQL -> Option A

4. Quick Check:

   ORM = Simplify database code [OK]

Hint: ORM means code replaces SQL for easier database work [OK]

Common Mistakes:

• Thinking ORM replaces Node.js runtime
• Confusing ORM with UI tools
• Assuming ORM manages hardware

2. Which of the following is the correct way to define a model in Sequelize?

easy

A. createModel('User', { name: 'string' })

B. sequelize.define('User', { name: DataTypes.STRING })

C. new Model('User', { name: String })

D. Model.defineUser({ name: DataType.String })

Solution

1. Step 1: Recall Sequelize model definition syntax

   Sequelize uses sequelize.define(modelName, attributes) to create models.

2. Step 2: Match options with correct syntax

   sequelize.define('User', { name: DataTypes.STRING }) matches the correct method and uses DataTypes.STRING properly.

3. Final Answer:

   sequelize.define('User', { name: DataTypes.STRING }) -> Option B

4. Quick Check:

   Sequelize model = sequelize.define() [OK]

Hint: Sequelize models use sequelize.define() with DataTypes [OK]

Common Mistakes:

• Using 'new Model' instead of sequelize.define
• Incorrect DataTypes usage
• Wrong method names like createModel

3. Given this Prisma schema snippet:

model Post {
  id    Int     @id @default(autoincrement())
  title String
  published Boolean @default(false)
}

What will be the default value of published when a new Post is created without specifying it?

medium

A. false

B. true

C. null

D. undefined

Solution

1. Step 1: Read the Prisma model definition

   The field published is Boolean with @default(false), meaning it defaults to false.

2. Step 2: Understand default behavior on creation

   If no value is given for published, Prisma sets it to the default, which is false.

3. Final Answer:

   false -> Option A

4. Quick Check:

   Prisma default Boolean = false [OK]

Hint: Look for @default() in Prisma schema for default values [OK]

Common Mistakes:

• Assuming default is true without checking
• Thinking default is null or undefined
• Ignoring @default directive

4. You wrote this Sequelize code:

const User = sequelize.define('User', {
  username: Sequelize.STRING,
  age: Sequelize.INTEGER
});

But you get an error: Sequelize.STRING is not a constructor. What is the likely fix?

medium

A. Change Sequelize.STRING to 'string' (a string literal)

B. Remove the model definition and use raw SQL instead

C. Import DataTypes from Sequelize and use DataTypes.STRING instead

D. Rename 'User' to 'Users' in define method

Solution

1. Step 1: Identify the cause of the error

   Sequelize.STRING is not a constructor because Sequelize exports DataTypes separately.

2. Step 2: Correct usage of DataTypes

   You should import DataTypes from Sequelize and use DataTypes.STRING and DataTypes.INTEGER in model definitions.

3. Final Answer:

   Import DataTypes from Sequelize and use DataTypes.STRING instead -> Option C

4. Quick Check:

   Use DataTypes.STRING, not Sequelize.STRING [OK]

Hint: Use DataTypes from Sequelize for types, not Sequelize directly [OK]

Common Mistakes:

• Using Sequelize.STRING instead of DataTypes.STRING
• Trying to fix by renaming model
• Switching to raw SQL unnecessarily

5. You want to fetch all users with their posts using Prisma. Which code snippet correctly fetches users including their posts?

hard

A. const users = await prisma.user.findAll({ include: ['posts'] });

B. const users = await prisma.user.findMany({ select: { posts: false } });

C. const users = await prisma.user.findMany({ where: { posts: null } });

D. const users = await prisma.user.findMany({ include: { posts: true } });

Solution

1. Step 1: Recall Prisma syntax for including related models

   Prisma uses include: { relatedModel: true } to fetch related data.

2. Step 2: Check each option for correct syntax

   const users = await prisma.user.findMany({ include: { posts: true } }); uses include: { posts: true } which is correct. const users = await prisma.user.findMany({ select: { posts: false } }); excludes posts, C filters by posts null, D uses wrong method name.

3. Final Answer:

   const users = await prisma.user.findMany({ include: { posts: true } }); -> Option D

4. Quick Check:

   Prisma include related = include: { posts: true } [OK]

Hint: Use include: { relatedModel: true } to fetch relations in Prisma [OK]

Common Mistakes:

• Using findAll instead of findMany in Prisma
• Using select to exclude instead of include to fetch
• Wrong syntax for including relations