Collections vs tables mental model in MongoDB - Quick Revision & Key Differences

Recall & Review

beginner

What is a collection in MongoDB?

A collection in MongoDB is like a folder that holds many documents. It is similar to a table in a traditional database but stores data in flexible, JSON-like documents.

beginner

How does a table in SQL differ from a collection in MongoDB?

A table in SQL has a fixed schema with rows and columns, while a MongoDB collection stores documents that can have different structures and fields.

beginner

Why is a MongoDB collection compared to a folder in real life?

Because just like a folder holds many files, a collection holds many documents. Each document can be different, just like files can be different types.

beginner

Can documents in the same MongoDB collection have different fields?

Yes, documents in the same collection can have different fields and structures, unlike rows in a SQL table which must follow the same columns.

intermediate

What is the main advantage of collections over tables in terms of data structure?

Collections allow flexible and dynamic data structures, so you can store different types of data together without needing to define a strict schema upfront.

In MongoDB, what is the closest equivalent to a SQL table?

A Collection

B Document

C Field

D Index

A collection in MongoDB is similar to a table in SQL because it groups many documents together.

Which of the following is true about MongoDB collections?

A All documents must have the same fields

B Collections have fixed columns like tables

C Documents can have different fields

D Collections store data in rows and columns

MongoDB collections store documents that can have different fields and structures.

What is a good real-life analogy for a MongoDB collection?

A A database server

B A spreadsheet

C A single file

D A folder holding files

A collection is like a folder that holds many documents (files).

Which statement best describes a SQL table compared to a MongoDB collection?

A Tables store JSON documents, collections store rows

B Tables have fixed columns, collections allow flexible document structures

C Tables have flexible schemas, collections have fixed schemas

D Tables and collections are exactly the same

SQL tables have fixed columns, while MongoDB collections allow documents with different structures.

Why might someone choose a MongoDB collection over a SQL table?

A To store data with flexible and changing structures

B To avoid using documents

C To use rows and columns format

D To enforce strict data types

MongoDB collections are chosen for their flexibility in storing documents with different fields and structures.

Explain the mental model comparing MongoDB collections and SQL tables.

Think about how files in a folder can be different, but rows in a spreadsheet follow the same columns.

Describe the main difference in data structure flexibility between collections and tables.

Consider how MongoDB handles data compared to traditional SQL databases.

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