Index direction (ascending vs descending) in MongoDB

Introduction

Indexes help find data faster in a database. The direction (ascending or descending) tells the database how to sort the data inside the index.

When you want to speed up searches that sort data from smallest to largest (ascending).

When you want to speed up searches that sort data from largest to smallest (descending).

When you create indexes for queries that use sorting to improve performance.

When you want to optimize queries that filter and sort on the same field.

When you want to control how data is stored in the index for better query speed.

Syntax

MongoDB

db.collection.createIndex({ fieldName: 1 })  // ascending index

db.collection.createIndex({ fieldName: -1 }) // descending index

Use 1 for ascending order and -1 for descending order.

The direction affects sorting and can improve query speed when used correctly.

Examples

This creates an ascending index on the age field, helping queries that sort or filter by age in ascending order.

MongoDB

db.users.createIndex({ age: 1 })

This creates a descending index on the orderDate field, helping queries that sort or filter by order date from newest to oldest.

MongoDB

db.orders.createIndex({ orderDate: -1 })

This creates a compound index: price ascending and rating descending. Useful for queries sorting by price ascending and rating descending.

MongoDB

db.products.createIndex({ price: 1, rating: -1 })

Sample Program

This example creates an ascending index on the price field in the products collection. Then it inserts some products and queries them sorted by price from low to high.

MongoDB

use shopDB

db.products.createIndex({ price: 1 })

// Insert sample data
 db.products.insertMany([
   { name: "Pen", price: 1.5 },
   { name: "Notebook", price: 3.0 },
   { name: "Pencil", price: 1.0 }
 ])

// Query sorted by price ascending
 db.products.find().sort({ price: 1 }).toArray()

Important Notes

Ascending and descending indexes both speed up queries, but choose direction based on how you sort your data.

MongoDB can use an ascending index for descending sorts and vice versa, but specifying direction helps optimize compound indexes.

Creating unnecessary indexes can slow down writes, so only create indexes you need.

Summary

Indexes store data in order: ascending (1) or descending (-1).

Choose index direction based on how you sort or filter your queries.

Compound indexes can mix ascending and descending directions for multiple fields.

Practice

1. What does the index direction 1 mean in MongoDB indexes?

easy

A. Descending order

B. No order

C. Ascending order

D. Random order

Solution

1. Step 1: Understand index direction values

   In MongoDB, index direction 1 means ascending order, and -1 means descending order.

2. Step 2: Match the value to the meaning

   Since the question asks about 1, it corresponds to ascending order.

3. Final Answer:

   Ascending order -> Option C

4. Quick Check:

   Index direction 1 = Ascending order [OK]

Hint: 1 means ascending, -1 means descending [OK]

Common Mistakes:

• Confusing 1 with descending order
• Thinking 1 means no order
• Mixing up ascending and descending

2. Which of the following is the correct syntax to create a descending index on the field age in MongoDB?

easy

A. db.collection.createIndex({ age: 1 })

B. db.collection.createIndex({ age: -1 })

C. db.collection.createIndex({ age: 'desc' })

D. db.collection.createIndex({ age: 'descending' })

Solution

1. Step 1: Recall MongoDB index syntax for direction

   MongoDB uses 1 for ascending and -1 for descending in index creation.

2. Step 2: Identify the correct descending syntax

   The correct way to create a descending index on age is { age: -1 }.

3. Final Answer:

   db.collection.createIndex({ age: -1 }) -> Option B

4. Quick Check:

   Descending index uses -1 [OK]

Hint: Use -1 for descending index direction [OK]

Common Mistakes:

• Using string values like 'desc' instead of -1
• Using 1 which means ascending
• Incorrect object syntax

3. Given the index { name: 1, score: -1 }, which query will use this index efficiently?

medium

A. db.collection.find().sort({ name: 1, score: -1 })

B. db.collection.find().sort({ name: -1, score: 1 })

C. db.collection.find().sort({ score: -1, name: 1 })

D. db.collection.find().sort({ name: 1 })

Solution

1. Step 1: Understand compound index direction

   The index sorts name ascending and score descending.

2. Step 2: Match query sort order with index

   Only the query sorting { name: 1, score: -1 } matches the index directions exactly, so it uses the index efficiently.

3. Final Answer:

   db.collection.find().sort({ name: 1, score: -1 }) -> Option A

4. Quick Check:

   Sort matches index directions exactly [OK]

Hint: Sort order must match index directions exactly [OK]

Common Mistakes:

• Reversing sort directions
• Changing field order in sort
• Using partial sort that doesn't match index

4. You created an index with { date: 1, price: -1 } but your query sorts by { price: -1, date: 1 }. What is the problem?

medium

A. The index fields order does not match the sort order

B. The index direction values are invalid

C. MongoDB does not support mixed ascending and descending indexes

D. The query syntax is incorrect

Solution

1. Step 1: Check index field order

   The index is created with fields date then price.

2. Step 2: Compare query sort order

   The query sorts by price first, then date, which does not match the index field order.

3. Final Answer:

   The index fields order does not match the sort order -> Option A

4. Quick Check:

   Field order in sort must match index order [OK]

Hint: Index and sort field order must match exactly [OK]

Common Mistakes:

• Assuming direction values are invalid
• Thinking MongoDB disallows mixed directions
• Blaming query syntax instead of order

5. You want to optimize queries that sort by category ascending and then by rating descending. Which index should you create?

hard

A. db.collection.createIndex({ rating: -1, category: 1 })

B. db.collection.createIndex({ category: -1, rating: 1 })

C. db.collection.createIndex({ rating: 1, category: -1 })

D. db.collection.createIndex({ category: 1, rating: -1 })

Solution

1. Step 1: Identify query sort order

   The queries sort by category ascending and rating descending.

2. Step 2: Create matching compound index

   The index must have category with direction 1 and rating with direction -1 in that order.

3. Final Answer:

   db.collection.createIndex({ category: 1, rating: -1 }) -> Option D

4. Quick Check:

   Index matches query sort directions and order [OK]

Hint: Match index fields and directions to query sort exactly [OK]

Common Mistakes:

• Reversing field order in index
• Swapping ascending and descending directions
• Creating index on wrong fields