Pretty printing and cursor behavior in MongoDB - Time & Space Complexity

Time Complexity: Pretty printing and cursor behavior

O(n)

Understanding Time Complexity

When working with MongoDB queries, it's important to understand how the way results are shown and handled affects performance.

We want to know how the time to get and display data changes as the amount of data grows.

Scenario Under Consideration

Analyze the time complexity of the following MongoDB query with pretty printing and cursor usage.

    const cursor = db.collection.find({ status: "active" });
    cursor.pretty();
    while (cursor.hasNext()) {
      printjson(cursor.next());
    }
    

This code finds all documents with status "active", formats them nicely, and prints each one.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Iterating over each document in the cursor to print it.
• How many times: Once for every matching document in the collection.

How Execution Grows With Input

As the number of matching documents grows, the time to print each one grows too.

Input Size (n)	Approx. Operations
10	10 prints
100	100 prints
1000	1000 prints

Pattern observation: The time grows directly with the number of documents to print.

Final Time Complexity

Time Complexity: O(n)

This means the time to print all documents grows in a straight line with the number of documents.

Common Mistake

[X] Wrong: "Pretty printing or using a cursor makes the query faster or slower by itself."

[OK] Correct: Pretty printing only changes how results look, not how many documents are processed. The cursor just helps fetch documents one by one, so time depends on how many documents match.

Interview Connect

Understanding how data retrieval and display scale helps you explain performance clearly and shows you know how databases handle results efficiently.

Self-Check

"What if we used a limit to only fetch 10 documents? How would that change the time complexity?"

Practice

1. What does the pretty() method do when used after a MongoDB query?

easy

A. Formats the output to be more readable with indentation and line breaks

B. Limits the number of documents returned by the query

C. Sorts the documents in ascending order

D. Deletes the documents matching the query

Solution

1. Step 1: Understand the purpose of pretty()

   The pretty() method formats the output of a query to make it easier to read by adding indentation and line breaks.

2. Step 2: Compare with other options

   Limiting, sorting, or deleting documents are done by other methods like limit(), sort(), or remove(), not pretty().

3. Final Answer:

   Formats the output to be more readable with indentation and line breaks -> Option A

4. Quick Check:

   pretty() improves readability [OK]

Hint: Remember: pretty() just makes output look nicer [OK]

Common Mistakes:

• Confusing pretty() with limit() or sort()
• Thinking pretty() changes the data
• Assuming pretty() affects query results count

2. Which of the following is the correct syntax to check if a MongoDB cursor has more documents to iterate?

easy

A. cursor.hasMore()

B. cursor.hasNext()

C. cursor.nextExists()

D. cursor.more()

Solution

1. Step 1: Recall cursor methods in MongoDB

   The correct method to check if a cursor has more documents is hasNext().

2. Step 2: Verify other options

   Methods like hasMore(), nextExists(), or more() do not exist in MongoDB cursor API.

3. Final Answer:

   cursor.hasNext() -> Option B

4. Quick Check:

   Use hasNext() to check cursor availability [OK]

Hint: Use hasNext() to check cursor's next document [OK]

Common Mistakes:

• Using non-existent cursor methods
• Confusing hasNext() with next()
• Assuming hasNext() returns the document itself

3. Given the following MongoDB shell commands, what will be the output?

var cursor = db.users.find({age: {$gt: 25}}).pretty();
while(cursor.hasNext()) {
  printjson(cursor.next());
}

medium

A. No output because cursor.next() is missing parentheses

B. Syntax error because pretty() cannot be chained with find()

C. All user documents with age greater than 25 printed in readable JSON format

D. Only the first user document with age greater than 25 printed

Solution

1. Step 1: Analyze the query and cursor usage

   The query finds users with age > 25 and applies pretty() to format output. The while loop uses hasNext() and next() to print each document.

2. Step 2: Understand the output behavior

   Each matching document is printed in readable JSON format until no documents remain.

3. Final Answer:

   All user documents with age greater than 25 printed in readable JSON format -> Option C

4. Quick Check:

   Cursor iterates all matching docs with pretty print [OK]

Hint: pretty() formats output; hasNext() and next() iterate all [OK]

Common Mistakes:

• Thinking pretty() breaks chaining
• Assuming only one document prints
• Forgetting to call next() as a function

4. You run this code in MongoDB shell:

var cursor = db.products.find().pretty();
if(cursor.hasNext) {
  printjson(cursor.next());
}

What is the problem with this code?

medium

A. hasNext is used without parentheses, so it does not check correctly

B. pretty() cannot be used with find()

C. next() should be called before hasNext()

D. printjson() cannot print cursor documents

Solution

1. Step 1: Identify method usage errors

   The method hasNext is used without parentheses, so it refers to the function itself, not its boolean result.

2. Step 2: Understand impact on code behavior

   Because hasNext is not called, the if condition always evaluates to true (function exists), causing unexpected behavior.

3. Final Answer:

   hasNext is used without parentheses, so it does not check correctly -> Option A

4. Quick Check:

   Always call hasNext() with parentheses [OK]

Hint: Call hasNext() with () to get boolean result [OK]

Common Mistakes:

• Using hasNext without parentheses
• Thinking pretty() causes error
• Calling next() before checking hasNext()

5. You want to print all documents from the orders collection where status is "shipped" in a readable format, but only 3 at a time to avoid memory overload. Which code snippet correctly achieves this?

hard

A. var cursor = db.orders.find({status: "shipped"}).batchSize(3); cursor.pretty(); while(cursor.hasNext()) { printjson(cursor.next()); }

B. var cursor = db.orders.find({status: "shipped"}).pretty(); for(var i=0; i<3; i++) { printjson(cursor.next()); }

C. var cursor = db.orders.find({status: "shipped"}).pretty(); while(cursor.hasNext()) { printjson(cursor.next()); if(i==3) break; }

D. var cursor = db.orders.find({status: "shipped"}).limit(3).pretty(); while(cursor.hasNext()) { printjson(cursor.next()); }

Solution

1. Step 1: Limit query results to 3 documents

   Using limit(3) restricts the cursor to only 3 documents matching the filter.

2. Step 2: Use pretty() to format output and iterate with hasNext()/next()

   Chaining pretty() formats output. The while loop prints each document until the 3 limited documents are exhausted.

3. Final Answer:

   var cursor = db.orders.find({status: "shipped"}).limit(3).pretty(); while(cursor.hasNext()) { printjson(cursor.next()); } -> Option D

4. Quick Check:

   limit(3) + pretty() + hasNext()/next() prints 3 formatted docs [OK]

Hint: Use limit(3) before pretty() and iterate with hasNext()/next() [OK]

Common Mistakes:

• Not using limit() to restrict documents
• Calling pretty() after iteration instead of chaining
• Incorrect loop control causing infinite or missing output