Rows vs documents thinking in MongoDB - Quick Revision & Key Differences

Recall & Review

beginner

What is a 'row' in traditional relational databases?

A row is a single record in a table that holds data for each column. Think of it like a single line in a spreadsheet representing one item or person.

beginner

What is a 'document' in MongoDB?

A document is a data record stored in a flexible, JSON-like format. It can hold nested information and different fields, like a detailed profile card with many sections.

intermediate

How does a document differ from a row in terms of structure?

A row has fixed columns with set data types, while a document can have varying fields and nested data, allowing more flexible and rich information in one place.

intermediate

Why might you choose documents over rows for some applications?

Documents let you store related data together, reducing the need to join tables. This is great for complex or changing data, like user profiles with different preferences.

beginner

Can documents in MongoDB have different fields in the same collection?

Yes! Unlike rows in tables, documents in the same collection can have different fields and structures, giving flexibility to store diverse data together.

In a relational database, what does a row represent?

A A flexible JSON-like object

B A nested data structure

C A collection of documents

D A single record with fixed columns

A row is a single record in a table with fixed columns.

Which of the following best describes a MongoDB document?

A A JSON-like object that can have nested fields

B A fixed set of columns

C A row in a table

D A relational table

MongoDB documents are JSON-like and can contain nested fields.

What is a key advantage of documents over rows?

A Documents require strict schema

B Rows are more flexible than documents

C Documents can store related data together without joins

D Rows can store nested data easily

Documents can store related data together, reducing the need for joins.

Can documents in the same MongoDB collection have different fields?

A No, all documents must have the same fields

B Yes, documents can have different fields

C Only if they are in different databases

D Only if they are in different tables

MongoDB allows documents in the same collection to have different fields.

Which data model is more like a spreadsheet row?

A Row

B JSON object

C Document

D Nested array

A row in a relational database is like a spreadsheet row.

Explain the main differences between rows in relational databases and documents in MongoDB.

Think about structure and flexibility.

Why might a developer choose to use documents instead of rows for storing user profile data?

Consider flexibility and data relationships.

Practice

1. Which statement best describes the difference between rows in SQL and documents in MongoDB?

easy

A. Rows are flexible and can change structure easily; documents are rigid.

B. Rows can store nested data; documents only store flat data.

C. Rows have fixed columns; documents can have varied fields and nested data.

D. Rows and documents are exactly the same in structure and use.

Solution

1. Step 1: Understand row structure in SQL

   Rows have fixed columns defined by the table schema, so each row has the same fields.

2. Step 2: Understand document structure in MongoDB

   Documents can have different fields and nested objects, allowing flexible and varied data.

3. Final Answer:

   Rows have fixed columns; documents can have varied fields and nested data. -> Option C

4. Quick Check:

   Rows = fixed, Documents = flexible [OK]

Hint: Rows = fixed columns, documents = flexible fields [OK]

Common Mistakes:

• Thinking documents must have same fields like rows
• Assuming rows can store nested data easily
• Confusing flexibility of documents with rows

2. Which of the following is the correct way to insert a document with nested fields in MongoDB?

easy

A. db.collection.insertOne({name: 'Alice', address: {city: 'NY', zip: 10001}})

B. INSERT INTO collection VALUES ('Alice', {city: 'NY', zip: 10001})

C. db.collection.insertOne(name: 'Alice', address: 'NY')

D. INSERT document {name: 'Alice', address: {city: 'NY', zip: 10001}}

Solution

1. Step 1: Identify MongoDB insert syntax

   MongoDB uses db.collection.insertOne() with a JSON-like document as argument.

2. Step 2: Check nested field format

   Nested fields are represented as nested objects inside the document, like address: {city: 'NY', zip: 10001}.

3. Final Answer:

   db.collection.insertOne({name: 'Alice', address: {city: 'NY', zip: 10001}}) -> Option A

4. Quick Check:

   Correct MongoDB insert with nested document [OK]

Hint: Use insertOne() with nested JSON object for documents [OK]

Common Mistakes:

• Using SQL INSERT syntax in MongoDB
• Passing fields outside an object
• Not using curly braces for nested fields

3. Given the collection users with documents like {name: 'Bob', scores: [10, 20, 30]}, what will db.users.find({scores: 20}) return?

medium

A. All documents where scores array contains 20

B. Documents where scores equals exactly 20

C. Documents where scores is missing

D. Syntax error because scores is an array

Solution

1. Step 1: Understand MongoDB query on array fields

   Querying {scores: 20} matches documents where the array 'scores' contains the value 20.

2. Step 2: Apply to example document

   Document with scores: [10, 20, 30] contains 20, so it matches and will be returned.

3. Final Answer:

   All documents where scores array contains 20 -> Option A

4. Quick Check:

   Query matches array elements [OK]

Hint: Querying array field matches if any element equals value [OK]

Common Mistakes:

• Thinking query matches whole array exactly
• Expecting syntax error for array query
• Confusing missing field with array content

4. You run this MongoDB query: db.orders.find({items: {product: 'Book'}}) but get no results. What is the likely problem?

medium

A. The field name 'product' is misspelled.

B. The query expects items to be an object, but items is an array of objects.

C. MongoDB does not support querying nested fields.

D. The collection name 'orders' is incorrect.

Solution

1. Step 1: Analyze query structure

   The query matches documents where 'items' exactly equals {product: 'Book'}.

2. Step 2: Understand data structure

   If 'items' is an array of objects, the query must use dot notation or $elemMatch to match inside array elements.

3. Final Answer:

   The query expects items to be an object, but items is an array of objects. -> Option B

4. Quick Check:

   Querying array needs $elemMatch or dot notation [OK]

Hint: Use $elemMatch or dot notation to query inside arrays [OK]

Common Mistakes:

• Querying array field as if it was a single object
• Assuming MongoDB can't query nested fields
• Ignoring data structure of the field

5. You want to store customer orders where each order can have multiple items with different quantities and prices. Which data model fits best in MongoDB?

hard

A. One document per item, with order info duplicated in each document.

B. Separate collections for orders and items, no embedding.

C. One flat table with one row per item, no nesting.

D. One document per order, with an array of item objects inside each document.

Solution

1. Step 1: Understand MongoDB document flexibility

   MongoDB documents can embed arrays of objects, ideal for storing multiple items inside one order document.

2. Step 2: Compare options for data modeling

   Embedding items inside order documents keeps related data together and fits MongoDB's document model better than duplication or flat tables.

3. Final Answer:

   One document per order, with an array of item objects inside each document. -> Option D

4. Quick Check:

   Embed related data in arrays for flexible documents [OK]

Hint: Embed related items as arrays inside order documents [OK]

Common Mistakes:

• Duplicating order info in many documents
• Using flat tables like SQL in MongoDB
• Splitting related data unnecessarily