Rows vs documents thinking in MongoDB - Visual Side-by-Side Comparison

Concept Flow - Rows vs documents thinking

Start: Data to store

↓

Choose storage style

↓

Rows

↓

Table

↓

Fixed columns

↓

Each row = 1 record

↓

Query data accordingly

This flow shows how data can be stored as rows in tables or as documents in collections, highlighting the difference in structure and flexibility.

Execution Sample

MongoDB

db.users.insertOne({name: "Alice", age: 30, hobbies: ["reading", "hiking"]})
db.users.find({name: "Alice"})

Insert a document with flexible fields into a MongoDB collection and then query it by name.

Execution Table

Step	Action	Data State	Result
1	Insert document {name: 'Alice', age: 30, hobbies: ['reading', 'hiking']}	Collection empty	Document added as one record
2	Query documents where name = 'Alice'	Collection has 1 document	Returns the inserted document
3	Insert document {name: 'Bob', age: 25}	Collection has 1 document	Document added, no hobbies field needed
4	Query all documents	Collection has 2 documents	Returns both documents with their fields
5	Attempt to query by hobbies	Collection has 2 documents	Returns only documents with hobbies field
6	End	No further actions	Execution stops

💡 No more queries or inserts; demonstration complete

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
Collection 'users'	empty	[{name: 'Alice', age: 30, hobbies: ['reading', 'hiking']}]	[{name: 'Alice', age: 30, hobbies: ['reading', 'hiking']}, {name: 'Bob', age: 25}]	same

Key Moments - 2 Insights

Why can documents have different fields while rows cannot?

Documents in MongoDB are flexible and can have different fields per record, as shown in steps 1 and 3 where 'hobbies' is present only in Alice's document. Rows in tables require fixed columns for all records.

What happens when you query a field that some documents don't have?

As in step 5, querying by 'hobbies' returns only documents that have that field. Documents without it are excluded, unlike rows where all columns exist for every row.

Visual Quiz - 3 Questions

Look at the execution table, what is the state of the collection after step 3?

A Empty collection

B Contains one document with name 'Alice' only

C Contains two documents: one for 'Alice' and one for 'Bob'

D Contains one document with name 'Bob' only

💡 Hint

Check the 'Data State' column in row for step 3 in the execution table

At which step does the query return only documents that have the 'hobbies' field?

A Step 5

B Step 2

C Step 4

D Step 1

💡 Hint

Look at the 'Result' column for step 5 in the execution table

If we added a new document with an extra field 'email', how would the collection state change?

A All documents would have the 'email' field added

B Only the new document would have the 'email' field

C The collection would reject the new document

D The 'email' field would replace 'hobbies' in all documents

💡 Hint

Recall that MongoDB documents can have flexible fields as shown in steps 1 and 3

Concept Snapshot

Rows vs Documents Thinking:
- Rows: fixed columns, each row same structure
- Documents: flexible fields, each document can differ
- Rows stored in tables; documents in collections
- Query returns full rows or matching documents
- Documents allow nested data and arrays
- Choose based on data flexibility needs

Full Transcript

This visual execution shows how data storage differs between rows and documents. Rows are fixed in structure, stored in tables, where each row has the same columns. Documents, like in MongoDB, are flexible and stored in collections. Each document can have different fields, including nested arrays. The example inserts documents with different fields and queries them, showing how queries return only matching documents. This helps understand why documents are more flexible than rows and how queries behave differently.