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.