Understanding Cursor

Welcome to the final unit of our MongoDB course! Throughout our lessons, we have delved deep into crucial aspects of MongoDB, such as projection, Comparison Query Operators, Logical Query Operators, Element Query Operators, and Array Query Operators. In this lesson, we turn our focus to an essential feature of MongoDB: working with cursors. While we briefly touched upon cursors in the first course of this series, we'll now dive deeper to understand their functionality and utility comprehensively.

In MongoDB, when you query a collection using the .find() method, what you actually get is a cursor object. Think of the cursor as a pointer that allows you to traverse through the result set one document at a time. This becomes especially useful when dealing with large datasets, as the cursor does not fetch all the data at once but retrieves it in manageable batches. This incremental fetching solves performance bottlenecks and reduces memory overhead.

Cursors in MongoDB come with two fundamental methods: next and hasNext.

• hasNext: This method checks whether there are more documents to be fetched from the database. It returns true if there are more documents and false otherwise.
• next: This method retrieves the next document in the cursor’s batch. If there are no more documents, it throws an error, so it's often used in conjunction with hasNext. It's important to note that the cursor initially points before the first element of the result set. The first call to next() returns the first element, and subsequent calls return the successive elements.

Here's a code snippet demonstrating hasNext and next cursor methods in action:

use comic_book_store_db

let cursor = db.comic_books.find({}, { title: 1, _id: 0 });
while (cursor.hasNext()) {
   printjson(cursor.next());
}

The while loop continues to execute as long as cursor.hasNext() returns true, processing each document one by one. Inside the loop, cursor.next() retrieves the next document, which is then printed using printjson. Note that we use a projection in the find method to return only the title field, excluding _id. This approach is efficient for handling large datasets incrementally, avoiding memory overload.