Firestore Database Basics

# CHAPTER 24

Firestore Database Basics #

1. Introduction #

• Install the cloudfirestore package.

• Write data to the cloud using .add() and .set().

• Read and listen to real-time database updates using StreamBuilder.

3. Collections and Documents (NoSQL Architecture) #

• Collection: A folder. (e.g., users, posts, products).

• Document: A specific file inside that folder. It contains data formatted exactly like JSON (Key-Value pairs). (e.g., a file containing John's bio, age, and name).

*Rule: A Collection can only hold Documents. A Document can hold data fields, AND it can hold Sub-Collections (a folder inside a file).* Path example: users (Collection) -> johnid (Document) -> name: "John"

1. 3. In your Flutter project, add: cloudfirestore: ^4.7.0.

5. CREATE: Writing Data to Firestore #

import 'package:cloud_firestore/cloud_firestore.dart';

Future<void> addUser() async {
  CollectionReference users = FirebaseFirestore.instance.collection(&#039;users');

  // .add() automatically generates a random, unique ID for this document!
  await users.add({
    &#039;name': 'Alice',
    &#039;age': 25,
    &#039;isPro': true,
  });
  print("User added to Cloud Firestore!");
}

*(If you want to specify the ID manually, for example, using the Firebase Auth User ID, use .doc(uid).set({...}) instead of .add().)*

6. UPDATE and DELETE #

// UPDATE: Change Alice's age to 26
Future<void> updateUser(String documentId) async {
  await FirebaseFirestore.instance.collection(&#039;users').doc(documentId).update({
    &#039;age': 26,
  });
}

// DELETE: Remove the document entirely
Future<void> deleteUser(String documentId) async {
  await FirebaseFirestore.instance.collection(&#039;users').doc(documentId).delete();
}

7. READ: Real-Time Data (StreamBuilder) #

class UserListScreen extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text("Real-Time Users")),
      // 1. StreamBuilder listens to the live Firestore pipe!
      body: StreamBuilder<QuerySnapshot>(
        stream: FirebaseFirestore.instance.collection(&#039;users').snapshots(),
        builder: (context, snapshot) {
          
          // 2. Handle loading state
          if (snapshot.connectionState == ConnectionState.waiting) {
            return Center(child: CircularProgressIndicator());
          }

          // 3. Extract the list of documents
          final List<DocumentSnapshot> documents = snapshot.data!.docs;

          // 4. Build a ListView!
          return ListView.builder(
            itemCount: documents.length,
            itemBuilder: (context, index) {
              // Access the JSON data map from the document
              Map<String, dynamic> data = documents[index].data() as Map<String, dynamic>;
              
              return ListTile(
                title: Text(data[&#039;name']),
                subtitle: Text("Age: ${data[&#039;age']}"),
              );
            },
          );
        },
      ),
    );
  }
}

8. Visual Learning: The Firestore Tree #

[ /users ] (Collection)
     |
     |-- [ 9xH72... ] (Document auto-ID)
     |       |-- name: "Alice"
     |       |-- age: 25
     |
     |-- [ z3P81... ] (Document auto-ID)
             |-- name: "Bob"
             |-- age: 30

9. Common Mistakes #

• Typos in Collection Names: If you write .collection('user') instead of .collection('users'), Firestore will not throw an error. Because it is NoSQL, it assumes you wanted to create a brand new, empty collection named 'user'. Always double-check your spelling!

10. Best Practices #

• Security Rules: Test mode leaves your database open to hackers. Before launching your app, you must write Firestore Security Rules in the console to ensure that only authenticated users can read/write data, and ideally, only the data that belongs to their specific Auth ID.

11. Practice Exercises #

1. 1. What is the equivalent of an SQL "Table" and "Row" in a NoSQL Firestore architecture?

1. 2. What method should you use if you want Firestore to generate a random, unique alphanumeric ID for your new document?

12. MCQs with Answers #

13. Interview Questions #

• Q: Explain the structural hierarchy of Cloud Firestore regarding Collections and Documents. Why can't a Collection hold data fields directly?

• Q: Contrast the usage of FutureBuilder with StreamBuilder when interacting with Firestore data. Provide a use case for each.

• Q: Explain how NoSQL databases differ from traditional relational SQL databases regarding predefined schemas and strict data types across documents within the same collection.

14. FAQs #

16. Next Chapter Recommendation #