Deletes the document referred to by the provided DocumentReference.
A reference to the document to be deleted.
This Transaction instance. Used for chaining method calls.
Reads the document referenced by the provided DocumentReference.
A reference to the document to be read.
A DocumentSnapshot of the read data.
Writes to the document referred to by the provided DocumentReference.
If the document does not exist yet, it will be created. If you pass
SetOptions, the provided data can be merged into the existing document.
A reference to the document to be set.
An object of the fields and values for the document.
Optionaloptions: { merge?: boolean; mergeFields?: (string | FieldPath)[] }An object to configure the set behavior.
This Transaction instance. Used for chaining method calls.
Updates fields in the document referred to by the provided
DocumentReference. The update will fail if applied to a document that
does not exist.
A reference to the document to be updated.
An object containing the fields and values with which to update the document. Fields can contain dots to reference nested fields within the document.
This Transaction instance. Used for chaining method calls.
Updates fields in the document referred to by the provided
DocumentReference. The update will fail if applied to a document that
does not exist.
Nested fields can be updated by providing dot-separated field path
strings or by providing FieldPath values.
A reference to the document to be updated.
The first field to update.
The first value.
Additional key/value pairs.
A Promise resolved once the data has been successfully written to the backend (Note that it won't resolve while you're offline).
A transaction is a set of reads and writes that are guaranteed to be atomic. Transactions are useful when you want to update a field's value based on its current value, or perform other conditional writes.