从RDBMS迁移至Firebase RTDB：Name与Value概念及树形数据结构适配咨询

Hey there! I totally get the confusion when moving from a relational database (RDBMS) with tables/rows/columns to Firebase Realtime Database's tree-based, key-value structure—it’s a big paradigm shift. Let’s use your User table example to demystify this, including the Name and Value concepts.

First: Let’s Recap Your RDBMS Example #

You have a User table with columns firstname, lastname, username, and a row with values:

firstname: James, lastname: John, username: Jhonathan

In RDBMS, data is rigidly structured into tables, where each row represents a single record, and columns define the attributes of that record.

How This Maps to Firebase RTDB’s Tree Structure #

Firebase RTDB stores data as a JSON-like tree of nodes, where every node is a key-value pair. There are no tables or rows—instead, you organize data into nested, hierarchical nodes. Here’s how your User record translates:

{
  "users": {
    "user_123": {
      "firstname": "James",
      "lastname": "John",
      "username": "Jhonathan"
    }
  }
}

Let’s break down the parallels to your RDBMS setup:

• RDBMS Table (User) → RTDB Top-Level Node ("users"): This acts as a container for all user records, just like your table.
• RDBMS Row → RTDB Child Node ("user_123"): Each row in your table becomes a unique child node under users. The user_123 is a unique identifier (like a primary key in RDBMS—Firebase can auto-generate these with push() if you don’t want to use custom IDs).
• RDBMS Columns → RTDB Nested Child Nodes: Each column name (firstname, lastname, username) becomes a child node under the user’s unique ID, with the column value as the node’s value.

Understanding Firebase’s Name and Value #

Every node in RTDB is defined by two parts:

• Name: This is the unique string identifier for the node (think of it as the "key" in a JSON object). It’s equivalent to:

  • A column name in RDBMS (when it’s an attribute node like firstname)
  • A primary key (when it’s a record node like user_123)
  • A table name (when it’s a top-level node like users)
    Note: Names can’t contain special characters like ., $, #, [, ], or /.

• Value: This is the data stored in the node. It can be:

  • A basic type: String, number, boolean, or null
  • A complex type: An array, or another nested tree of nodes (like the user_123 node’s value, which contains all the user’s attributes)

Using your example again:

• For the node firstname, Name is "firstname" and Value is "James"
• For the node user_123, Name is "user_123" and Value is the object containing firstname, lastname, and username
• For the node users, Name is "users" and Value is the object containing all user nodes

A Quick Tip for Transitioning #

Instead of trying to mirror your RDBMS schema exactly, think about how your app will query data. For example:

• If you often need to look up users by username, you might add a secondary index node like "usernames": {"Jhonathan": "user_123"} to make that query fast.
• Firebase’s tree structure lets you denormalize data (duplicate it in places) to avoid expensive joins, which is a common practice unlike in RDBMS.

Once you start thinking in terms of nested key-value pairs rather than rows and columns, it’ll all click!

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