From 35ed81a20a14b0a0f73b97a4209b43574491d140 Mon Sep 17 00:00:00 2001 From: David Frahm Date: Sun, 27 Aug 2017 12:49:00 -0500 Subject: [PATCH] Clarification of non-destructive updates --- docs/2-retrieving-data-as-objects.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/2-retrieving-data-as-objects.md b/docs/2-retrieving-data-as-objects.md index 3f217fb5a..ecd9ebac1 100644 --- a/docs/2-retrieving-data-as-objects.md +++ b/docs/2-retrieving-data-as-objects.md @@ -82,7 +82,7 @@ The table below highlights some of the common methods on the `FirebaseObjectObse | method | | | ---------|--------------------| | `set(value: any)` | Replaces the current value in the database with the new value specified as the parameter. This is called a **destructive** update, because it deletes everything currently in place and saves the new value. | -| `update(value: Object)` | Updates the current value with in the database with the new value specified as the parameter. This is called a **non-destructive** update, because it only updates the values specified. | +| `update(value: Object)` | Updates the current value with in the database with the new value specified as the parameter. This is called a **non-destructive** update, because it only updates the values specified. Note: Only values at the key level are non-destructive. | | `remove()` | Deletes all data present at that location. Same as calling `set(null)`. | ## Returning promises