Firestore in Datastore mode V1 API - Class Google::Cloud::Datastore::V1::PropertyTransform (v1.3.0)

Equivalent numbers of different types (e.g. 3L and 3.0) are considered equal when checking if a value is missing. NaN is equal to NaN, and the null value is equal to the null value. If the input contains multiple equivalent values, only the first will be considered.

The corresponding transform result will be the null value.

Note: The following fields are mutually exclusive: append_missing_elements, set_to_server_value, increment, maximum, minimum, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

Equivalent numbers of different types (e.g. 3L and 3.0) are considered equal when checking if a value is missing. NaN is equal to NaN, and the null value is equal to the null value. If the input contains multiple equivalent values, only the first will be considered.

The corresponding transform result will be the null value.

Note: The following fields are mutually exclusive: append_missing_elements, set_to_server_value, increment, maximum, minimum, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

Equivalent numbers of different types (e.g. 3L and 3.0) are considered equal when checking if a value is missing. NaN is equal to NaN, and the null value is equal to the null value. If the input contains multiple equivalent values, only the first will be considered.

The corresponding transform result will be the null value.

Note: The following fields are mutually exclusive: append_missing_elements, set_to_server_value, increment, maximum, minimum, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the given value. If either of the given value or the current property value are doubles, both values will be interpreted as doubles. Double arithmetic and representation of double values follows IEEE 754 semantics. If there is positive/negative integer overflow, the property is resolved to the largest magnitude positive/negative integer.

Note: The following fields are mutually exclusive: increment, set_to_server_value, maximum, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the given value. If either of the given value or the current property value are doubles, both values will be interpreted as doubles. Double arithmetic and representation of double values follows IEEE 754 semantics. If there is positive/negative integer overflow, the property is resolved to the largest magnitude positive/negative integer.

Note: The following fields are mutually exclusive: increment, set_to_server_value, maximum, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the given value. If either of the given value or the current property value are doubles, both values will be interpreted as doubles. Double arithmetic and representation of double values follows IEEE 754 semantics. If there is positive/negative integer overflow, the property is resolved to the largest magnitude positive/negative integer.

Note: The following fields are mutually exclusive: increment, set_to_server_value, maximum, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the given value. If a maximum operation is applied where the property and the input value are of mixed types (that is - one is an integer and one is a double) the property takes on the type of the larger operand. If the operands are equivalent (e.g. 3 and 3.0), the property does not change. 0, 0.0, and -0.0 are all zero. The maximum of a zero stored value and zero input value is always the stored value. The maximum of any numeric value x and NaN is NaN.

Note: The following fields are mutually exclusive: maximum, set_to_server_value, increment, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the given value. If a maximum operation is applied where the property and the input value are of mixed types (that is - one is an integer and one is a double) the property takes on the type of the larger operand. If the operands are equivalent (e.g. 3 and 3.0), the property does not change. 0, 0.0, and -0.0 are all zero. The maximum of a zero stored value and zero input value is always the stored value. The maximum of any numeric value x and NaN is NaN.

Note: The following fields are mutually exclusive: maximum, set_to_server_value, increment, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the given value. If a maximum operation is applied where the property and the input value are of mixed types (that is - one is an integer and one is a double) the property takes on the type of the larger operand. If the operands are equivalent (e.g. 3 and 3.0), the property does not change. 0, 0.0, and -0.0 are all zero. The maximum of a zero stored value and zero input value is always the stored value. The maximum of any numeric value x and NaN is NaN.

Note: The following fields are mutually exclusive: maximum, set_to_server_value, increment, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the input value. If a minimum operation is applied where the property and the input value are of mixed types (that is - one is an integer and one is a double) the property takes on the type of the smaller operand. If the operands are equivalent (e.g. 3 and 3.0), the property does not change. 0, 0.0, and -0.0 are all zero. The minimum of a zero stored value and zero input value is always the stored value. The minimum of any numeric value x and NaN is NaN.

Note: The following fields are mutually exclusive: minimum, set_to_server_value, increment, maximum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the input value. If a minimum operation is applied where the property and the input value are of mixed types (that is - one is an integer and one is a double) the property takes on the type of the smaller operand. If the operands are equivalent (e.g. 3 and 3.0), the property does not change. 0, 0.0, and -0.0 are all zero. The minimum of a zero stored value and zero input value is always the stored value. The minimum of any numeric value x and NaN is NaN.

Note: The following fields are mutually exclusive: minimum, set_to_server_value, increment, maximum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

This must be an integer or a double value. If the property is not an integer or double, or if the property does not yet exist, the transformation will set the property to the input value. If a minimum operation is applied where the property and the input value are of mixed types (that is - one is an integer and one is a double) the property takes on the type of the smaller operand. If the operands are equivalent (e.g. 3 and 3.0), the property does not change. 0, 0.0, and -0.0 are all zero. The minimum of a zero stored value and zero input value is always the stored value. The minimum of any numeric value x and NaN is NaN.

Note: The following fields are mutually exclusive: minimum, set_to_server_value, increment, maximum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

Property paths (a list of property names separated by dots (.)) may be used to refer to properties inside entity values. For example foo.bar means the property bar inside the entity property foo.

If a property name contains a dot . or a backlslash \, then that name must be escaped.

Property paths (a list of property names separated by dots (.)) may be used to refer to properties inside entity values. For example foo.bar means the property bar inside the entity property foo.

If a property name contains a dot . or a backlslash \, then that name must be escaped.

Property paths (a list of property names separated by dots (.)) may be used to refer to properties inside entity values. For example foo.bar means the property bar inside the entity property foo.

If a property name contains a dot . or a backlslash \, then that name must be escaped.

Equivalent numbers of different types (e.g. 3L and 3.0) are considered equal when deciding whether an element should be removed. NaN is equal to NaN, and the null value is equal to the null value. This will remove all equivalent values if there are duplicates.

The corresponding transform result will be the null value.

Note: The following fields are mutually exclusive: remove_all_from_array, set_to_server_value, increment, maximum, minimum, append_missing_elements. If a field in that set is populated, all other fields in the set will automatically be cleared.

Equivalent numbers of different types (e.g. 3L and 3.0) are considered equal when deciding whether an element should be removed. NaN is equal to NaN, and the null value is equal to the null value. This will remove all equivalent values if there are duplicates.

The corresponding transform result will be the null value.

Note: The following fields are mutually exclusive: remove_all_from_array, set_to_server_value, increment, maximum, minimum, append_missing_elements. If a field in that set is populated, all other fields in the set will automatically be cleared.

Equivalent numbers of different types (e.g. 3L and 3.0) are considered equal when deciding whether an element should be removed. NaN is equal to NaN, and the null value is equal to the null value. This will remove all equivalent values if there are duplicates.

The corresponding transform result will be the null value.

Note: The following fields are mutually exclusive: remove_all_from_array, set_to_server_value, increment, maximum, minimum, append_missing_elements. If a field in that set is populated, all other fields in the set will automatically be cleared.

Note: The following fields are mutually exclusive: set_to_server_value, increment, maximum, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

Note: The following fields are mutually exclusive: set_to_server_value, increment, maximum, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.

Note: The following fields are mutually exclusive: set_to_server_value, increment, maximum, minimum, append_missing_elements, remove_all_from_array. If a field in that set is populated, all other fields in the set will automatically be cleared.