Sequelize ORM setup in Express - Mini Project: Build & Apply

Sequelize ORM setup

📖 Scenario: You are building a simple Express app that needs to store user data in a database. To manage the database easily, you will set up Sequelize ORM.

🎯 Goal: Set up Sequelize ORM in your Express app by creating a Sequelize instance, configuring the database connection, defining a User model, and syncing the model with the database.

📋 What You'll Learn

Create a Sequelize instance connected to a SQLite database file named database.sqlite

Define a User model with username (string) and email (string) fields

Sync the User model with the database

Export the User model for use in other parts of the app

💡 Why This Matters

🌍 Real World

Sequelize ORM helps developers manage database operations easily without writing raw SQL. It is widely used in Node.js backend applications.

💼 Career

Knowing how to set up and use Sequelize is valuable for backend developer roles working with Node.js and relational databases.

1

Create Sequelize instance

Create a constant called Sequelize by requiring the sequelize package. Then create a constant called sequelize by instantiating Sequelize with a SQLite database file named database.sqlite using the dialect option set to 'sqlite' and storage option set to 'database.sqlite'.

Express

# Your code here

Hint

Use require('sequelize') to get Sequelize. Then create a new Sequelize instance with the correct options for SQLite.

2

Define User model

Define a constant called User by calling sequelize.define with the model name 'User' and an object describing two fields: username and email, both of type Sequelize.STRING.

Express

const { Sequelize } = require('sequelize');

const sequelize = new Sequelize({
  dialect: 'sqlite',
  storage: 'database.sqlite'
});

// Define User model here
# Your code here

Hint

Use sequelize.define('User', { username: Sequelize.STRING, email: Sequelize.STRING }) to create the model.

3

Sync User model with database

Call sequelize.sync() to sync all defined models with the database.

Express

const { Sequelize } = require('sequelize');

const sequelize = new Sequelize({
  dialect: 'sqlite',
  storage: 'database.sqlite'
});

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

// Sync models with database
# Your code here

Hint

Call sequelize.sync() to create tables if they don't exist.

4

Export User model

Export the User model using module.exports = User.

Express

const { Sequelize } = require('sequelize');

const sequelize = new Sequelize({
  dialect: 'sqlite',
  storage: 'database.sqlite'
});

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

sequelize.sync();

// Export User model
# Your code here

Hint

Use module.exports = User to export the model.

Practice

1. What is the main purpose of Sequelize in an Express application?

easy

A. To connect and interact with databases using JavaScript objects

B. To handle HTTP requests and routing

C. To style the frontend components

D. To manage user authentication

Solution

1. Step 1: Understand Sequelize's role

   Sequelize is an ORM that helps connect your app to databases using JavaScript objects.

2. Step 2: Compare with other Express tasks

   Handling HTTP requests or styling is done by other tools, not Sequelize.

3. Final Answer:

   To connect and interact with databases using JavaScript objects -> Option A

4. Quick Check:

   Sequelize = Database connection [OK]

Hint: Sequelize = database ORM, not routing or styling [OK]

Common Mistakes:

• Confusing Sequelize with Express routing
• Thinking Sequelize manages frontend styling
• Assuming Sequelize handles authentication directly

2. Which of the following is the correct way to create a Sequelize instance for a PostgreSQL database named 'mydb' with user 'user' and password 'pass'?

easy

A. const sequelize = new Sequelize({ database: 'mydb', username: 'user', password: 'pass' });

B. const sequelize = Sequelize.connect('mydb', 'user', 'pass', { dialect: 'postgres' });

C. const sequelize = new Sequelize('mydb', 'user', 'pass', { dialect: 'postgres' });

D. const sequelize = new Sequelize('postgres://user:pass@localhost/mydb');

Solution

1. Step 1: Recall Sequelize constructor syntax

   The Sequelize constructor takes database name, username, password, and options including dialect.

2. Step 2: Check each option

   const sequelize = new Sequelize('mydb', 'user', 'pass', { dialect: 'postgres' }); matches the correct syntax. const sequelize = Sequelize.connect('mydb', 'user', 'pass', { dialect: 'postgres' }); uses a non-existent connect method. const sequelize = new Sequelize({ database: 'mydb', username: 'user', password: 'pass' }); uses wrong parameter structure. const sequelize = new Sequelize('postgres://user:pass@localhost/mydb'); is valid but uses a connection string, which is not asked here.

3. Final Answer:

   const sequelize = new Sequelize('mydb', 'user', 'pass', { dialect: 'postgres' }); -> Option C

4. Quick Check:

   Sequelize constructor = new Sequelize(db, user, pass, options) [OK]

Hint: Sequelize constructor uses new Sequelize(db, user, pass, options) [OK]

Common Mistakes:

• Using Sequelize.connect instead of new Sequelize
• Passing options incorrectly
• Confusing connection string with parameters

3. Given the following Sequelize model definition, what will be the output of console.log(User.name);?

const User = sequelize.define('User', {
  name: {
    type: Sequelize.STRING,
    allowNull: false
  }});

medium

A. 'User'

B. undefined

C. Sequelize.STRING

D. An error because 'name' is a field, not a property

Solution

1. Step 1: Understand model definition

   The first argument 'User' is the model name and is accessible as User.name property.

2. Step 2: Check what User.name returns

   User.name returns the model name string 'User', not the field value or type.

3. Final Answer:

   'User' -> Option A

4. Quick Check:

   Model name = User.name = 'User' [OK]

Hint: Model name is stored in User.name, not fields [OK]

Common Mistakes:

• Confusing field 'name' with model name
• Expecting field value instead of model name
• Assuming User.name is undefined

4. You wrote this code to sync your Sequelize models but get an error:

await sequelize.sync({ force: true });
console.log('Database synced!');

What is the most likely cause of the error?

medium

A. Sequelize instance not created

B. Missing async function wrapper for await

C. force option is invalid

D. Incorrect sync method name

Solution

1. Step 1: Check usage of await

   Using await requires the code to be inside an async function.

2. Step 2: Verify other options

   sync is correct method, force is valid option, and Sequelize instance must exist before this code.

3. Final Answer:

   Missing async function wrapper for await -> Option B

4. Quick Check:

   await needs async function [OK]

Hint: Always use await inside async functions [OK]

Common Mistakes:

• Using await outside async function
• Misspelling sync method
• Misunderstanding force option

5. You want to set up Sequelize in your Express app to connect to a MySQL database named 'shop' with username 'root' and password 'pass' using separate parameters for database, username, password, and options, and define a 'Product' model with fields 'title' (string) and 'price' (decimal). Which code snippet correctly sets up Sequelize and defines this model?

hard

A. const sequelize = new Sequelize('mysql://root:pass@localhost/shop');
const Product = sequelize.define('Product', {
title: Sequelize.STRING,
price: Sequelize.DECIMAL
});

B. const sequelize = new Sequelize('shop', 'root', 'pass', { dialect: 'mysql' });
const Product = sequelize.define('Product', {
title: 'string',
price: 'decimal'
});

C. const sequelize = new Sequelize('mysql://root:pass@localhost/shop');
const Product = sequelize.define('Product', {
title: { type: 'string' },
price: { type: 'decimal' }
});

D. const sequelize = new Sequelize('shop', 'root', 'pass', { dialect: 'mysql' });
const Product = sequelize.define('Product', {
title: { type: Sequelize.STRING },
price: { type: Sequelize.DECIMAL }
});

Solution

1. Step 1: Check Sequelize instance creation

   const sequelize = new Sequelize('shop', 'root', 'pass', { dialect: 'mysql' }); const Product = sequelize.define('Product', { title: { type: Sequelize.STRING }, price: { type: Sequelize.DECIMAL } }); correctly uses new Sequelize with database, user, password, and dialect options for MySQL using separate parameters.

2. Step 2: Verify model field definitions

   const sequelize = new Sequelize('shop', 'root', 'pass', { dialect: 'mysql' }); const Product = sequelize.define('Product', { title: { type: Sequelize.STRING }, price: { type: Sequelize.DECIMAL } }); defines fields with type property using Sequelize.STRING and Sequelize.DECIMAL, which is correct syntax.

3. Step 3: Identify errors in other options

   Options A and D use connection string instead of separate parameters. const sequelize = new Sequelize('shop', 'root', 'pass', { dialect: 'mysql' }); const Product = sequelize.define('Product', { title: 'string', price: 'decimal' }); uses separate parameters but incorrect field definitions with string literals instead of Sequelize data types.

4. Final Answer:

   Correct Sequelize setup and model definition with proper data types -> Option D

5. Quick Check:

   Sequelize setup + model fields = const sequelize = new Sequelize('shop', 'root', 'pass', { dialect: 'mysql' }); const Product = sequelize.define('Product', { title: { type: Sequelize.STRING }, price: { type: Sequelize.DECIMAL } }); [OK]

Hint: Use Sequelize data types with { type: Sequelize.TYPE } syntax [OK]

Common Mistakes:

• Using string literals instead of Sequelize data types
• Incorrect Sequelize constructor parameters
• Omitting type property in model fields