Collections vs tables mental model in MongoDB - Visual Side-by-Side Comparison

Concept Flow - Collections vs tables mental model

Start: Data Storage

↓

Relational DB

→Table

↓

Rows & Columns

↓

MongoDB

→Collection

↓

Documents (JSON-like)

This flow shows how data is stored differently: relational databases use tables with rows and columns, while MongoDB uses collections with documents.

Execution Sample

MongoDB

db.users.insertOne({name: "Alice", age: 30})
db.users.find()

Insert a document into the 'users' collection and then retrieve all documents from it.

Execution Table

Step	Action	Data Structure	Content	Result
1	Insert document into 'users'	Collection 'users'	{"name": "Alice", "age": 30}	Document added
2	Find all documents in 'users'	Collection 'users'	[{"name": "Alice", "age": 30}]	Returns list with one document
3	Insert another document	Collection 'users'	{"name": "Bob", "age": 25}	Document added
4	Find all documents in 'users'	Collection 'users'	[{"name": "Alice", "age": 30}, {"name": "Bob", "age": 25}]	Returns list with two documents
5	End	-	-	No more actions

💡 No more commands to execute

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
users collection	empty	[{"name": "Alice", "age": 30}]	[{"name": "Alice", "age": 30}]	[{"name": "Alice", "age": 30}, {"name": "Bob", "age": 25}]	[{"name": "Alice", "age": 30}, {"name": "Bob", "age": 25}]	[{"name": "Alice", "age": 30}, {"name": "Bob", "age": 25}]

Key Moments - 2 Insights

Why is a MongoDB collection not exactly like a SQL table?

Unlike SQL tables that have fixed columns, MongoDB collections store flexible JSON-like documents that can have different fields. See execution_table steps 1 and 3 where documents have similar but not fixed structure.

Can documents in the same collection have different fields?

Yes, documents in a collection can have different fields. This is different from tables where each row must follow the same column structure. The execution_table shows documents inserted with 'name' and 'age', but others could have different fields.

Visual Quiz - 3 Questions

Look at the execution_table, what does the 'users' collection contain after step 2?

A Two documents with names 'Alice' and 'Bob'

B Empty collection

C One document with name 'Alice' and age 30

D One document with name 'Bob' and age 25

💡 Hint

Check the 'Content' column at step 2 in execution_table

At which step does the 'users' collection first contain two documents?

A Step 4

B Step 3

C Step 2

D Step 1

💡 Hint

Look at the 'Content' column in execution_table rows for steps 3 and 4

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

A All documents must have 'email' field

B Only the new document has 'email', others stay the same

C The collection rejects the document

D The collection converts all documents to have 'email'

💡 Hint

MongoDB collections allow flexible document structures as shown in key_moments about different fields

Concept Snapshot

Collections in MongoDB are like tables in SQL but store flexible JSON-like documents.
Documents can have different fields, unlike fixed columns in tables.
You insert documents into collections and query them similarly to rows in tables.
This flexibility allows easy storage of varied data without strict schema.
Think: Collection = Table, Document = Row but with flexible structure.

Full Transcript

This lesson shows the difference between collections in MongoDB and tables in relational databases. Collections hold documents, which are like rows but can have different fields. We traced inserting documents into a 'users' collection and retrieving them. Unlike tables with fixed columns, collections allow flexible document structures. This helps beginners understand MongoDB's flexible data model compared to rigid SQL tables.

Practice

1. Which of the following best describes a MongoDB collection compared to a SQL table?

easy

A. A collection requires a strict schema like SQL tables.

B. A collection stores data in fixed rows and columns.

C. A collection stores flexible documents without fixed columns.

D. A collection cannot store multiple records.

Solution

1. Step 1: Understand SQL tables

   SQL tables store data in rows and columns with a fixed schema, meaning each row has the same columns.

2. Step 2: Understand MongoDB collections

   MongoDB collections store documents that can have different fields and structures, so they are flexible and schema-less.

3. Final Answer:

   A collection stores flexible documents without fixed columns. -> Option C

4. Quick Check:

   Collections = flexible documents [OK]

Hint: Collections are flexible; tables have fixed columns [OK]

Common Mistakes:

• Thinking collections have fixed columns like tables
• Assuming collections require strict schemas
• Believing collections cannot hold multiple documents

2. Which of the following is the correct way to create a collection named users in MongoDB?

easy

A. db.createCollection('users');

B. db.users.create();

C. CREATE TABLE users;

D. CREATE COLLECTION users;

Solution

1. Step 1: Recall MongoDB syntax for creating collections

   MongoDB uses the method db.createCollection('name') to create a collection explicitly.

2. Step 2: Check other options

   CREATE COLLECTION users; and C use SQL syntax, which is invalid in MongoDB. db.users.create(); is not a valid MongoDB command.

3. Final Answer:

   db.createCollection('users'); -> Option A

4. Quick Check:

   MongoDB collection creation = db.createCollection() [OK]

Hint: Use db.createCollection('name') to create collections [OK]

Common Mistakes:

• Using SQL syntax like CREATE TABLE
• Trying to call create() on collection name
• Omitting quotes around collection name

3. Given a MongoDB collection products with documents:

{"name": "Pen", "price": 1.5}

{"name": "Notebook", "price": 3.0, "color": "blue"}

What will db.products.find({}) return?

medium

A. All documents including fields like name, price, and color if present.

B. Only documents with the price field.

C. Only documents with the color field.

D. An error because documents have different fields.

Solution

1. Step 1: Understand find({}) query

   The query find({}) returns all documents in the collection regardless of their fields.

2. Step 2: Check document fields

   Documents can have different fields in MongoDB collections; this does not cause errors or filtering.

3. Final Answer:

   All documents including fields like name, price, and color if present. -> Option A

4. Quick Check:

   find({}) returns all documents [OK]

Hint: find({}) returns all documents regardless of fields [OK]

Common Mistakes:

• Thinking find({}) filters by fields
• Expecting errors due to different document structures
• Assuming only documents with certain fields are returned

4. You tried to insert documents with different fields into a MongoDB collection but got an error. What is the most likely cause?

medium

A. MongoDB collections require all documents to have the same fields.

B. MongoDB does not allow inserting multiple documents.

C. You forgot to create the collection before inserting.

D. You used SQL INSERT syntax instead of MongoDB insert methods.

Solution

1. Step 1: Recall MongoDB insert syntax

   MongoDB uses insertOne() or insertMany() methods, not SQL INSERT statements.

2. Step 2: Understand document flexibility

   MongoDB collections allow documents with different fields; this does not cause errors.

3. Final Answer:

   You used SQL INSERT syntax instead of MongoDB insert methods. -> Option D

4. Quick Check:

   MongoDB insert = insertOne()/insertMany() [OK]

Hint: Use MongoDB insertOne()/insertMany(), not SQL INSERT [OK]

Common Mistakes:

• Assuming MongoDB requires fixed schema
• Not creating collection first (MongoDB auto-creates collections)
• Believing MongoDB forbids multiple inserts

5. You want to migrate a SQL table with fixed columns to MongoDB. Which approach best fits MongoDB's collection model?

hard

A. Keep the exact SQL schema and enforce it strictly in MongoDB.

B. Store each row as a document with the same fields, but allow optional fields for future flexibility.

C. Convert the table into multiple collections, each with one column as documents.

D. Store all rows as a single large document with arrays for each column.

Solution

1. Step 1: Understand MongoDB document flexibility

   MongoDB collections store documents that can have different fields, so keeping the same fields but allowing optional ones fits well.

2. Step 2: Evaluate other options

   Convert the table into multiple collections, each with one column as documents. breaks data into many collections unnecessarily. Keep the exact SQL schema and enforce it strictly in MongoDB. tries to enforce strict schema, which MongoDB does not require. Store all rows as a single large document with arrays for each column. stores all data in one document, which is inefficient and not recommended.

3. Final Answer:

   Store each row as a document with the same fields, but allow optional fields for future flexibility. -> Option B

4. Quick Check:

   MongoDB collections = flexible documents per row [OK]

Hint: Migrate rows as flexible documents with optional fields [OK]

Common Mistakes:

• Trying to enforce strict SQL schema in MongoDB
• Splitting columns into separate collections
• Storing all rows in one big document