Ordered vs unordered inserts in MongoDB - Visual Side-by-Side Comparison

Concept Flow - Ordered vs unordered inserts

Start Insert Operation

↓

Is Ordered Insert?

No→Insert All Documents, Continue on Errors

|Yes↓

Insert Documents One by One

↓

Stop on First Error

↓

End Insert Operation

The insert operation checks if it is ordered. If ordered, it inserts documents one by one and stops on the first error. If unordered, it inserts all documents and continues even if some fail.

Execution Sample

MongoDB

db.collection.insertMany([
  {name: "Alice"},
  {name: "Bob"},
  {name: "Alice"}
], {ordered: true})

Insert three documents with ordered:true, stops if a duplicate key error occurs.

Execution Table

Step	Document Inserted	Error?	Action	Result
1	{"name": "Alice"}	No	Insert document	Success
2	{"name": "Bob"}	No	Insert document	Success
3	{"name": "Alice"}	Yes (duplicate key)	Stop insertion	Error returned, no more inserts

💡 Insertion stops at step 3 due to duplicate key error with ordered:true

Variable Tracker

Variable	Start	After 1	After 2	After 3 (final)
InsertedCount	0	1	2	2
ErrorOccurred	false	false	false	true

Key Moments - 2 Insights

Why does the insertion stop after the third document in ordered mode?

Because with ordered:true, MongoDB stops inserting documents as soon as it encounters an error, as shown in execution_table step 3.

What happens if ordered:false is used and an error occurs?

MongoDB tries to insert all documents regardless of errors, so errors do not stop the process. This differs from the ordered:true case in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the InsertedCount after step 2?

A 2

B 1

C 3

D 0

💡 Hint

Check the variable_tracker row for InsertedCount after step 2

At which step does the insertion stop due to an error in ordered mode?

A Step 1

B Step 3

C Step 2

D Insertion never stops

💡 Hint

See execution_table row 3 where error occurs and insertion stops

If ordered:false was used, how would the insertion behave on error?

A Insert only the first document

B Stop immediately at first error

C Skip error and continue inserting remaining documents

D Fail without inserting any documents

💡 Hint

Refer to key_moments explanation about unordered inserts continuing despite errors

Concept Snapshot

MongoDB insertMany() can be ordered or unordered.
- ordered:true inserts documents one by one and stops on first error.
- ordered:false inserts all documents, continuing despite errors.
Use ordered:false for faster bulk inserts when some errors are acceptable.
Errors in ordered mode stop the process immediately.
Unordered mode reports all errors after attempting all inserts.

Full Transcript

This visual execution shows how MongoDB handles ordered versus unordered inserts. When ordered:true is set, documents are inserted one at a time. If an error occurs, such as a duplicate key, the insertion stops immediately. This is shown in the execution table where the third document causes an error and the process halts. The variable tracker shows the count of successfully inserted documents stops increasing after the error. In contrast, unordered inserts (ordered:false) would continue inserting all documents even if some cause errors. This behavior is important to understand for controlling insert operations and error handling in MongoDB.