Realtime Database

Since v2.3.0

Edit data

With a paid plan, Fuego changes Realtime Database data in the details panel, in the table and from each node's menu. A save in the details panel shows what will change before it is sent and, unless it is saved field by field, is refused when someone changed the node since you opened it. Every change stops at the paths you made read-only in Fuego.

Before you start

  • Changing data needs a paid plan (Individual, Team or the Lifetime Deal). On the Free plan you can browse and read your databases, while the commands that change data carry a crown and open the plans.
  • Who writes. Fuego writes with the project’s own credentials, as Admin (the security rules are not checked). In a tab that reads as a user, it writes as that user and the rules decide; an activity in the background always runs as Admin.
  • What stops a change: a read-only team sublicense, a project kept read-only in Fuego (Adding a Firebase project), a path or whole database made read-only in Fuego, an unverified database synced from another computer, or an anonymized tab (click Load real values to edit).

Edit a node in the details panel

  1. Right-click a row in the Tree, Panel or Table view and choose Edit…, or select it and press Space.
  2. Change the value: a single value lets you choose Text, Number, Boolean or JSON; an object opens in the JSON editor.
  3. Click Save (or use the keyboard shortcut on macOS: Shortcuts). Fuego shows what you opened next to what will be saved, and lists what the save deletes. Nothing is sent until you confirm.

Reset drops your unsaved changes, Reload reads the node again, and Delete removes it (Delete nodes). What you do not change stays exactly as the database holds it: a number keeps its digits (1.0 stays 1.0) and priorities are preserved.

Checks before a save

Fuego checks the value before sending anything:

  • Invalid JSON, invalid keys, paths deeper than 32 keys or longer than 768 bytes from the root, or a changed priority are refused.
  • Arrays offer Convert to objects, which turns them into an object with keys 0, 1, 2, and so on.
  • Empty objects are not stored by the Realtime Database: the review lists those your save would drop, and a save that leaves nothing in the node opens the delete dialog instead.
  • When the node has a JSON schema, Validate with the JSON schema highlights mismatches without blocking Save.

Large nodes

Fuego reads a node of up to 1 MB for editing automatically. Between 1 MB and 10 MB, the panel offers Edit (downloads up to 10 MB); beyond 10 MB, edit its children one by one.

Who the save writes as

  • In a tab that reads as a user, the button reads Save as {identity} and your security rules decide. If the rules refuse the change, your edits stay in the editor and Save as Admin… offers to save them with the project’s credentials after a review.
  • In the quick view window, which always reads and writes as Admin, the button reads Save as Admin.

Field by field

When the database answers without a version Fuego can check the save against, the save is written field by field (last write wins), and Save also offers Replace node… to overwrite the whole node.

Edit a value in the table

In the Table view, a cell that holds a text, a number, true or false shows a pencil (Edit value). Click it to edit the value in place:

  • Enter saves, Esc cancels, Shift+Enter starts a new line.
  • Edit… opens the node in the details panel.
  • If the value changed in the database since you opened it, the editor shows the new value and offers Replace with mine or Use the server value.

Add a child

Use Add child in the tab’s toolbar, or Actions ▸ Add child… / Push child… in a node’s menu. Choose the Parent, the Key (Push ID or This key) and the Value (typed value, JSON or Server time in milliseconds). A Push ID is generated by the database so children stay in creation order.

Other changes from the Actions menu

A node’s Actions menu (in its right-click menu and in the details panel) also offers:

  • Rename key…, Move to… and Copy to…. When the node is too large for one request, it runs as a background activity: Export, import and bulk jobs.
  • Server value ▸ Set to server timestamp and Increment… (a negative number subtracts), on single values.
  • Delete… (Delete nodes).

Delete nodes

Delete one node with Delete in the details panel or Delete… in its Actions menu, or delete selected rows with Delete {count}… in the selection menu (Selected: {count}).

The dialog counts the children to delete. A large delete—the root of the database, 1,000 children or more, 10 nodes or more, or a size Fuego cannot count—asks you to type the node’s key (or the database’s name for the root or multiple nodes) to confirm. A delete too large for one request runs in small steps in the background (Delete as an activity: see Export, import and bulk jobs).

When the node changed meanwhile

A save in the details panel only goes through when the node is still as you opened it (unless saved field by field). When someone changed it, Fuego writes nothing and shows In the database now next to Yours:

  • Reapply my changes: applies your changes to the latest version so you can check and save again.
  • Use the database’s version: drops your changes.
  • Replace with mine…: writes your version over the database’s after a review (or Create it again with mine… if the node was deleted).

When Fuego sees the node change while you are still editing it (for example with Live on), the panel shows Show changes and Discard mine and reload.

Read-only in Fuego

Protect a path or a whole database from accidental edits in Fuego. In a node’s menu (or the tab’s Data menu), choose Settings ▸:

  • Read-only in Fuego to protect the node and everything under it;
  • Whole database read-only in Fuego to protect the entire database.

Fuego then refuses every change there—in the explorer, in jobs, from the command line and from the AI assistant—on every plan. Nothing changes in Firebase: your apps and the Firebase console can still write there. Click the lock icon next to the protected node or database (Make writable…) to unlock it. With a paid plan, settings sync carries read-only paths across your computers.

Limits that stay

  • Priorities are read-only: every save preserves existing priorities and refuses changes to them.
  • The root of the database cannot be renamed, moved, copied or set to a server value.
  • The database’s write size limit: Firebase refuses a single write that exceeds the database’s Size limit of one write (Database settings).
  • A change is sent once: if the connection drops after a write is sent, Fuego tells you it may have gone through and asks you to reload the node before retrying.