Skip to content

Commit b0d40c0

Browse files
David Frahmdavideast
authored andcommitted
Clarification of non-destructive updates (#1126)
1 parent 8767f73 commit b0d40c0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/2-retrieving-data-as-objects.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ The table below highlights some of the common methods on the `FirebaseObjectObse
8282
| method | |
8383
| ---------|--------------------|
8484
| `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. |
85-
| `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. |
85+
| `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. |
8686
| `remove()` | Deletes all data present at that location. Same as calling `set(null)`. |
8787

8888
## Returning promises

0 commit comments

Comments
 (0)