Associations (hasMany, belongsTo) in Express - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Understanding hasMany association behavior

Given the following Sequelize models, what will be the output of console.log(user.posts.length) after fetching the user with posts?

Express

const User = sequelize.define('User', { name: DataTypes.STRING });
const Post = sequelize.define('Post', { title: DataTypes.STRING });
User.hasMany(Post);
Post.belongsTo(User);

async function test() {
  const user = await User.findOne({ where: { id: 1 }, include: [Post] });
  console.log(user.posts.length);
}

A Always 0, because posts are not loaded automatically

B The number of posts related to the user (e.g., 3 if user has 3 posts)

C Undefined, because posts is not a property on user

D Throws a runtime error because include is not valid here

💡 Hint

Remember that hasMany creates an array property on the source model instance when included.

The hasMany association adds a plural property (posts) to the User instance. When you include Post in the query, Sequelize loads all related posts into that array. So user.posts.length gives the count of posts.

❓ state_output

intermediate

belongsTo association foreign key value

Consider these Sequelize models and code snippet. What will be the value of post.userId after creating a post linked to a user?

Express

const User = sequelize.define('User', { name: DataTypes.STRING });
const Post = sequelize.define('Post', { title: DataTypes.STRING });
Post.belongsTo(User);
User.hasMany(Post);

async function test() {
  const user = await User.create({ name: 'Alice' });
  const post = await Post.create({ title: 'Hello', userId: user.id });
  console.log(post.userId);
}

A The id of the user (e.g., 1)

B Undefined, because userId is not set automatically

C Null, because belongsTo does not set foreign keys

D Throws an error because userId is not a defined field

💡 Hint

Check how belongsTo creates a foreign key field on the source model.

The belongsTo association adds a foreign key field (userId) to the Post model. When creating a post with userId set to the user's id, the value is stored and accessible.

📝 Syntax

advanced

Correct association declaration syntax

Which option correctly declares a hasMany and belongsTo association between Author and Book models in Sequelize?

Express

const Author = sequelize.define('Author', { name: DataTypes.STRING });
const Book = sequelize.define('Book', { title: DataTypes.STRING });

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

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

C Author.hasMany(Book, { foreignKey: 'authorId' }); Book.belongsTo(Author, { foreignKey: 'authorId' });

D Author.hasMany(Book, { foreignKey: 'bookId' }); Book.belongsTo(Author, { foreignKey: 'authorId' });

💡 Hint

Check that foreign keys match on both sides of the association.

Option C correctly sets the foreign key authorId on Book for both hasMany and belongsTo. Option C misses explicit foreign keys but is valid if defaults are used. Option C reverses the relationship. Option C mismatches foreign keys.

🔧 Debug

advanced

Debugging missing association data in query

Given these models and query, why does user.posts return undefined?

Express

const User = sequelize.define('User', { name: DataTypes.STRING });
const Post = sequelize.define('Post', { title: DataTypes.STRING });
User.hasMany(Post);
Post.belongsTo(User);

async function test() {
  const user = await User.findOne({ where: { id: 1 } });
  console.log(user.posts);
}

A Because the query did not include the Post model, so posts are not loaded

B Because hasMany association was not declared correctly

C Because user.posts is always undefined in Sequelize

D Because the user with id 1 does not exist

💡 Hint

Think about how Sequelize loads associated data.

Sequelize only loads associated data if you specify it in the query using include. Without include: Post, the posts property is not set and remains undefined.

🧠 Conceptual

expert

Understanding cascading deletes with associations

In Sequelize, if you want deleting a User to automatically delete all their Posts, which association option should you use?

A Post.belongsTo(User, { onUpdate: 'RESTRICT' });

B User.hasMany(Post, { onUpdate: 'CASCADE' });

C Post.belongsTo(User, { onDelete: 'SET NULL' });

D User.hasMany(Post, { onDelete: 'CASCADE' });

💡 Hint

Think about which side controls deletion behavior and what 'CASCADE' means.

The onDelete: 'CASCADE' option on hasMany tells Sequelize to delete all related posts when the user is deleted. Other options control update behavior or set foreign keys to null, not cascading deletes.

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