如何在Firestore文档中添加子集合？Web应用实现及替代方案咨询

Hey there! Let's work through this together—adding subcollections in Firestore is totally doable, so chances are you just hit a small snag in your code. Let's start with the correct approach for Firestore, then tackle your question about switching to Realtime Database.

First off, a quick Firestore 101: Subcollections are tied to parent documents, but the parent document doesn't even need to exist beforehand—Firestore will automatically create it if you add a document to its subcollection. Here's how to implement this properly with both the modern modular SDK and the older namespaced version.

Using Firebase v9+ (Modular SDK) #

This is the recommended approach for new projects. Make sure you've initialized your Firestore instance correctly first:

import { doc, collection, addDoc } from "firebase/firestore";
import { db } from "./your-firebase-config"; // Import your initialized Firestore instance

async function addSubcollectionEntry() {
  try {
    // 1. Create a reference to the parent document
    const parentDocRef = doc(db, "users", "user1"); // Replace with your parent collection/doc ID
    // 2. Create a reference to the subcollection
    const subcollectionRef = collection(parentDocRef, "orders"); // "orders" is your subcollection name
    // 3. Add a new document to the subcollection (auto-generates an ID)
    const newDoc = await addDoc(subcollectionRef, {
      item: "Wireless Mouse",
      price: 29.99,
      orderDate: new Date()
    });
    console.log("Subcollection document added successfully! ID:", newDoc.id);
  } catch (error) {
    console.error("Failed to add subcollection document:", error);
  }
}

// Call the function to execute
addSubcollectionEntry();

Using Firebase v8 (Namespaced SDK) #

If you're working with an older codebase, here's the equivalent code:

// Assuming you've initialized Firebase and Firestore already
const db = firebase.firestore();

async function addSubcollection() {
  try {
    const newDoc = await db
      .collection("users")
      .doc("user1")
      .collection("orders")
      .add({
        item: "Mechanical Keyboard",
        price: 89.99,
        orderDate: new Date()
      });
    console.log("Subcollection document ID:", newDoc.id);
  } catch (err) {
    console.error("Error adding subcollection:", err);
  }
}

Common Pitfalls to Check #

If your code isn't working, these are the most likely issues:

• Firestore Security Rules: By default, Firestore blocks unauthenticated writes. Make sure your rules allow write access to the subcollection. For testing, you can use a temporary rule (don't leave this in production!):

  rules_version = '2';
  service cloud.firestore {
    match /databases/{database}/documents {
      match /{document=**} {
        allow read, write: if request.auth != null; // Require authenticated users
      }
    }
  }
  

• Incorrect Paths: Double-check your collection and document IDs—typos here are super common!
• Uninitialized Firestore Instance: Ensure you've properly initialized Firebase and Firestore before making calls.

Whether this makes sense depends entirely on your use case:

• Stick with Firestore if: You need complex queries, flexible document/collection structures, or robust indexing. Firestore's subcollection model is designed specifically for hierarchical data like user orders, blog posts with comments, etc.
• Consider Realtime Database if: Your data is focused on real-time sync (like chat apps or live leaderboards) and has a simpler, flat JSON structure. It's also a bit cheaper for high-throughput, small-data operations.

If you do decide to go with Realtime Database, here's how to add nested data:

Adding Nested Data in Realtime Database (Web) #

Realtime Database uses a JSON tree structure, so nested data is written directly to the path:

import { getDatabase, ref, set, push } from "firebase/database";
import { db } from "./your-firebase-config"; // Import your Realtime Database instance

// Option 1: Add a nested document with a specific ID
async function addNestedDataWithID() {
  try {
    const db = getDatabase();
    await set(ref(db, "users/user1/orders/order001"), {
      item: "Bluetooth Speaker",
      price: 49.99,
      orderDate: new Date().toISOString()
    });
    console.log("Nested data added successfully!");
  } catch (err) {
    console.error("Error adding nested data:", err);
  }
}

// Option 2: Auto-generate an ID using push()
async function addNestedDataAutoID() {
  const db = getDatabase();
  const newOrderRef = push(ref(db, "users/user1/orders")); // Generates a unique ID
  await set(newOrderRef, {
    item: "USB-C Charger",
    price: 19.99,
    orderDate: new Date().toISOString()
  });
}

Final Recommendation #

Unless your use case specifically calls for Realtime Database's real-time sync or simpler structure, I'd recommend sticking with Firestore. The subcollection feature is perfect for hierarchical data, and fixing your existing code (checking rules, paths, or initialization) should get it working.

内容的提问来源于stack exchange，提问作者user8167002