Document-collection data model in Firebase - Step-by-Step Execution

Process Flow - Document-collection data model

Start

↓

Create Collection

↓

Add Document

↓

Document Contains Fields

↓

Add Subcollection (optional)

↓

Repeat for more documents or collections

↓

Query or Update Documents

↓

End

This flow shows how you start with a collection, add documents with fields, optionally add subcollections, and then query or update documents.

Execution Sample

Firebase

db.collection('users').doc('user1').set({name: 'Anna', age: 30})

This code creates a 'users' collection, adds a document 'user1' with fields name and age.

Process Table

Step	Action	Collection	Document ID	Fields Added	Result
1	Create collection if not exists	users			Collection 'users' ready
2	Create document 'user1'	users	user1		Document 'user1' created
3	Set fields in 'user1'	users	user1	{name: 'Anna', age: 30}	Fields saved in 'user1'
4	Add subcollection 'orders' to 'user1'	users/user1	orders		Subcollection 'orders' created
5	Add document 'order1' in 'orders'	users/user1/orders	order1	{item: 'book', price: 10}	Document 'order1' saved
6	Query documents in 'users'	users			Returns documents like 'user1'
7	Update field 'age' in 'user1'	users	user1	{age: 31}	Field 'age' updated
8	End				No more actions

💡 All documents and collections created and updated as per steps.

Status Tracker

Variable	Start	After Step 3	After Step 5	After Step 7	Final
Collection 'users'	empty	contains 'user1'	contains 'user1' with subcollection 'orders'	same	same
Document 'user1'	none	{name: 'Anna', age: 30}	{name: 'Anna', age: 30, orders subcollection}	{name: 'Anna', age: 31, orders subcollection}	same
Subcollection 'orders'	none	none	contains 'order1'	same	same
Document 'order1'	none	none	{item: 'book', price: 10}	same	same

Key Moments - 3 Insights

Why do we create a collection before adding documents?

Collections organize documents. Step 1 shows collection 'users' is ready before adding document 'user1' in step 2.

Can documents contain other collections?

Yes, documents can have subcollections. Step 4 shows adding 'orders' subcollection inside 'user1' document.

What happens when we update a field in a document?

The field value changes but the document stays. Step 7 updates 'age' from 30 to 31 in 'user1'.

Visual Quiz - 3 Questions

Look at the execution table, what fields does document 'user1' have after step 3?

A {name: 'Anna', age: 30}

B {item: 'book', price: 10}

C {age: 31}

D No fields yet

💡 Hint

Check the 'Fields Added' column at step 3 in the execution table.

At which step is the subcollection 'orders' created under 'user1'?

A Step 2

B Step 4

C Step 5

D Step 7

💡 Hint

Look for the action mentioning subcollection creation in the execution table.

If we change the update in step 7 to set age to 32, what changes in variable_tracker?

A Document 'user1' age changes to 32 after step 7

B No change in document 'user1'

C Subcollection 'orders' is removed

D Collection 'users' is deleted

💡 Hint

Check the 'Document user1' row in variable_tracker after step 7.

Concept Snapshot

Document-collection data model in Firebase:
- Collections hold documents.
- Documents hold fields (key-value pairs).
- Documents can have subcollections.
- Use .collection() and .doc() to navigate.
- Use .set() to add or update fields.
- Organize data hierarchically for easy queries.

Full Transcript

The document-collection data model in Firebase organizes data into collections and documents. You start by creating a collection, then add documents with fields inside it. Documents can also have subcollections, which are collections nested inside documents. You can add, update, and query documents easily. For example, creating a 'users' collection, adding a 'user1' document with name and age fields, then adding an 'orders' subcollection inside 'user1' with order documents. Updating a field changes its value but keeps the document intact. This model helps keep data structured and easy to access.

Practice

1. In Firebase's document-collection data model, what is the main container that holds documents?

easy

A. A collection

B. A table

C. A row

D. A field

Solution

1. Step 1: Understand Firebase data structure

   Firebase stores data in documents, and these documents are grouped inside collections.

2. Step 2: Identify the container for documents

   The container that holds multiple documents is called a collection, not a table, row, or field.

3. Final Answer:

   A collection -> Option A

4. Quick Check:

   Documents are inside collections [OK]

Hint: Remember: collections hold documents, like folders hold files [OK]

Common Mistakes:

• Confusing collections with tables from SQL
• Thinking documents are inside fields
• Mixing up rows with documents

2. Which of the following is the correct way to reference a document named user123 inside a collection users in Firebase?

easy

A. db.collection('users').doc('user123')

B. db.doc('users').doc('user123')

C. db.collection('user123').doc('users')

D. db.users('user123')

Solution

1. Step 1: Recall Firebase syntax for document reference

   To get a document inside a collection, use collection('name').doc('id').

2. Step 2: Match the correct syntax

   db.collection('users').doc('user123') uses db.collection('users').doc('user123'), which is the standard way.

3. Final Answer:

   db.collection('users').doc('user123') -> Option A

4. Quick Check:

   Use collection then doc to reference documents [OK]

Hint: Use collection('name').doc('id') to get a document [OK]

Common Mistakes:

• Swapping collection and doc order
• Using dot notation like db.users('user123')
• Using doc with full path incorrectly

3. Given this code snippet in Firebase:

const docRef = db.collection('books').doc('book1');
await docRef.set({ title: 'Learn Firebase', pages: 150 });
const snapshot = await db.collection('books').get();
const titles = snapshot.docs.map(doc => doc.data().title);
console.log(titles);

What will be printed in the console if the 'books' collection was empty before?

medium

A. []

B. ['book1']

C. ['Learn Firebase']

D. Error: Cannot read property 'title' of undefined

Solution

1. Step 1: Understand the code flow

   The code adds a document 'book1' with title and pages to 'books' collection, then fetches all documents in 'books'.

2. Step 2: Analyze the output of mapping titles

   Since 'books' was empty before, after adding 'book1', the collection has one document with title 'Learn Firebase'. Mapping titles returns ['Learn Firebase'].

3. Final Answer:

   ['Learn Firebase'] -> Option C

4. Quick Check:

   Added one doc, so titles list has one title [OK]

Hint: After set(), collection has that document; map titles returns it [OK]

Common Mistakes:

• Thinking snapshot is empty before set()
• Confusing document ID with title
• Expecting error due to async code

4. Consider this Firebase code snippet:

const userRef = db.collection('users').doc('user1');
userRef.get().then(doc => {
  if (doc.exists) {
    console.log(doc.data().name);
  } else {
    console.log('No such document!');
  }
});

If the document 'user1' does not exist, what will be printed?

medium

A. undefined

B. 'No such document!'

C. Error: doc.data() is undefined

D. null

Solution

1. Step 1: Check the existence condition

   The code checks if doc.exists is true before accessing data.

2. Step 2: Understand behavior when document missing

   If the document does not exist, doc.exists is false, so it prints 'No such document!'.

3. Final Answer:

   'No such document!' -> Option B

4. Quick Check:

   doc.exists false triggers else block [OK]

Hint: Check doc.exists before accessing data to avoid errors [OK]

Common Mistakes:

• Trying to access data without checking doc.exists
• Expecting undefined or null instead of message
• Confusing doc.exists with doc.data()

5. You want to store a list of users, each with multiple addresses, in Firebase. Which data model best fits this scenario?

hard

A. One document 'users' containing all users and their addresses as nested arrays

B. A single collection 'addresses' with documents containing user info and address combined

C. Multiple collections named after each user containing address documents

D. A collection 'users' with documents for each user, each containing a subcollection 'addresses' with address documents

Solution

1. Step 1: Understand hierarchical data in Firebase

   Firebase supports subcollections inside documents, which is ideal for related nested data.

2. Step 2: Choose the best structure for users and their multiple addresses

   Using a 'users' collection with each user document having an 'addresses' subcollection keeps data organized and scalable.

3. Final Answer:

   A collection 'users' with documents for each user, each containing a subcollection 'addresses' with address documents -> Option D

4. Quick Check:

   Use subcollections for nested related data [OK]

Hint: Use subcollections for nested lists like addresses per user [OK]

Common Mistakes:

• Storing all users and addresses in one big document
• Mixing user and address data in one collection without hierarchy
• Creating many collections named after users