Why Associations (hasMany, belongsTo) in Express? - Purpose & Use Cases

The Big Idea

Discover how simple connections between data models can save you hours of confusing code!

The Scenario

Imagine you have two lists: one for authors and one for books. You want to connect each book to its author manually by searching through both lists every time you need to find related data.

The Problem

Manually linking data like this is slow and confusing. You might forget to update both lists, causing errors. It's hard to keep track of which books belong to which authors, especially as data grows.

The Solution

Associations like hasMany and belongsTo let you define clear relationships between data models. This way, you can easily fetch all books for an author or find the author of a book without messy manual code.

Before vs After

✗ Before

const authorBooks = books.filter(book => book.authorId === author.id);

✓ After

Author.hasMany(Book);
Book.belongsTo(Author);
const authorBooks = await author.getBooks();

What It Enables

It enables simple, reliable access to related data, making your code cleaner and your app faster.

Real Life Example

Think of a blog where each post belongs to a user. Using associations, you can quickly show all posts by a user or find who wrote a post without extra searching.

Key Takeaways

Manual data linking is slow and error-prone.

Associations define clear, automatic relationships between models.

This makes data fetching easier, cleaner, and more reliable.

Practice

1. In Express with Sequelize, what does the hasMany association represent between two models?

easy

A. One model instance can have multiple related instances of another model.

B. One model instance belongs to exactly one instance of another model.

C. Two models have no relationship.

D. Models share the same database table.

Solution

1. Step 1: Understand the meaning of hasMany

   The hasMany association means one record in a model can be linked to many records in another model.

2. Step 2: Compare with other associations

   belongsTo means one record belongs to one other record, not many.

3. Final Answer:

   One model instance can have multiple related instances of another model. -> Option A

4. Quick Check:

   hasMany = one-to-many [OK]

Hint: hasMany means one item links to many others [OK]

Common Mistakes:

• Confusing hasMany with belongsTo
• Thinking hasMany means no relation
• Assuming hasMany means shared tables

2. Which of the following is the correct syntax to define a belongsTo association in Sequelize for a model Comment that belongs to Post?

easy

A. Comment.belongsTo(Post);

B. Post.belongsTo(Comment);

C. Comment.hasMany(Post);

D. Post.hasMany(Comment);

Solution

1. Step 1: Identify the direction of belongsTo

   The model that belongs to another calls belongsTo on itself with the other model as argument.

2. Step 2: Apply to Comment and Post

   Since Comment belongs to Post, the syntax is Comment.belongsTo(Post);.

3. Final Answer:

   Comment.belongsTo(Post); -> Option A

4. Quick Check:

   belongsTo called on child model [OK]

Hint: belongsTo called on the model that belongs [OK]

Common Mistakes:

• Reversing the models in belongsTo
• Using hasMany instead of belongsTo
• Calling belongsTo on the wrong model

3. Given the following Sequelize association code:

Author.hasMany(Book);
Book.belongsTo(Author);

What will await author.getBooks() return if author is an Author instance?

medium

A. An error because belongsTo is missing.

B. An array of Book instances related to that author.

C. Undefined, because getBooks is not a valid method.

D. A single Book instance related to that author.

Solution

1. Step 1: Understand hasMany and belongsTo setup

   Author has many Books, and each Book belongs to one Author, so Sequelize creates methods like getBooks on Author instances.

2. Step 2: Check what getBooks returns

   getBooks returns an array of all Book instances linked to that Author.

3. Final Answer:

   An array of Book instances related to that author. -> Option B

4. Quick Check:

   hasMany creates plural get method returning array [OK]

Hint: hasMany creates getPlural() returning array [OK]

Common Mistakes:

• Expecting a single instance instead of array
• Thinking getBooks is invalid method
• Ignoring belongsTo association

4. Consider this Sequelize association code with an error:

Order.hasMany(Item);
Item.belongsTo(Order);

// Later in code
const order = await Order.findByPk(1);
const items = await order.getItem();

What is the error and how to fix it?

medium

A. Order should use belongsTo, not hasMany.

B. belongsTo should be called on Order, not Item.

C. Method getItem() is incorrect; should be getItems() because hasMany creates plural getter.

D. findByPk is not a valid Sequelize method.

Solution

1. Step 1: Identify the association methods

   Order hasMany Item means Sequelize creates getItems() method on Order instances, not getItem().

2. Step 2: Fix the method call

   Change order.getItem() to order.getItems() to correctly fetch related items.

3. Final Answer:

   Method getItem() is incorrect; should be getItems() because hasMany creates plural getter. -> Option C

4. Quick Check:

   hasMany creates plural get method [OK]

Hint: hasMany creates plural get method, use getItems() [OK]

Common Mistakes:

• Using singular get method for hasMany
• Confusing belongsTo direction
• Thinking findByPk is invalid

5. You have two models: User and Profile. Each User has one Profile, and each Profile belongs to one User. Which Sequelize associations correctly represent this, and what methods will be available on User instances?

hard

A. User.belongsTo(Profile); Profile.hasOne(User); with user.getProfile() method.

B. User.hasMany(Profile); Profile.belongsTo(User); with user.getProfiles() method.

C. Profile.hasOne(User); User.belongsTo(Profile); with user.getProfile() method.

D. User.hasOne(Profile); Profile.belongsTo(User); with user.getProfile() method.

Solution

1. Step 1: Identify one-to-one relationship

   Each User has one Profile means hasOne is used, not hasMany.

2. Step 2: Set belongsTo on Profile

   Profile belongs to User, so Profile.belongsTo(User); is correct.

3. Step 3: Check available methods

   User instances get getProfile() method for the single related Profile.

4. Final Answer:

   User.hasOne(Profile); Profile.belongsTo(User); with user.getProfile() method. -> Option D

5. Quick Check:

   One-to-one uses hasOne + belongsTo [OK]

Hint: One-to-one uses hasOne + belongsTo with singular get method [OK]

Common Mistakes:

• Using hasMany for one-to-one
• Reversing belongsTo direction
• Expecting plural get method for one-to-one