- 3.51.0 (latest)
- 3.50.1
- 3.46.0
- 3.45.0
- 3.44.0
- 3.43.0
- 3.42.0
- 3.41.0
- 3.40.1
- 3.39.0
- 3.38.0
- 3.37.0
- 3.36.0
- 3.35.1
- 3.34.0
- 3.33.0
- 3.32.0
- 3.31.0
- 3.30.0
- 3.29.0
- 3.28.0
- 3.27.1
- 3.26.0
- 3.25.0
- 3.24.0
- 3.23.0
- 3.22.2
- 3.21.0
- 3.20.0
- 3.19.0
- 3.18.0
- 3.17.0
- 3.16.0
- 3.15.1
- 3.14.1
- 3.13.0
- 3.12.1
- 3.11.1
- 3.10.0
- 3.9.0
- 3.8.0
- 3.7.0
- 3.6.0
- 3.5.0
- 3.4.0
- 3.3.0
- 3.2.0
- 3.1.0
- 3.0.0
- 2.1.1
- 2.0.0
- 1.19.3
- 1.18.0
- 1.17.1
- 1.16.0
- 1.15.1
- 1.14.0
- 1.13.0
- 1.12.0
- 1.11.0
- 1.10.0
Mutation(mapping=None, *, ignore_unknown_fields=False, **kwargs)
A modification to one or more Cloud Spanner rows. Mutations can be
applied to a Cloud Spanner database by sending them in a
Commit][google.spanner.v1.Spanner.Commit]
call.
Attributes
Name | Description |
insert |
`.mutation.Mutation.Write`
Insert new rows in a table. If any of the rows already exist, the write or transaction fails with error ``ALREADY_EXISTS``. |
update |
`.mutation.Mutation.Write`
Update existing rows in a table. If any of the rows does not already exist, the transaction fails with error ``NOT_FOUND``. |
insert_or_update |
`.mutation.Mutation.Write`
Like `insert][google.spanner.v1.Mutation.insert]`, except that if the row already exists, then its column values are overwritten with the ones provided. Any column values not explicitly written are preserved. When using `insert_or_update][google.spanner.v1.Mutation.insert_or_update]`, just as when using `insert][google.spanner.v1.Mutation.insert]`, all ``NOT NULL`` columns in the table must be given a value. This holds true even when the row already exists and will therefore actually be updated. |
replace |
`.mutation.Mutation.Write`
Like `insert][google.spanner.v1.Mutation.insert]`, except that if the row already exists, it is deleted, and the column values provided are inserted instead. Unlike `insert_or_update][google.spanner.v1.Mutation.insert_or_update]`, this means any values not explicitly written become ``NULL``. In an interleaved table, if you create the child table with the ``ON DELETE CASCADE`` annotation, then replacing a parent row also deletes the child rows. Otherwise, you must delete the child rows before you replace the parent row. |
delete |
`.mutation.Mutation.Delete`
Delete rows from a table. Succeeds whether or not the named rows were present. |
Inheritance
builtins.object > proto.message.Message > MutationClasses
Delete
Delete(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Arguments to delete][google.spanner.v1.Mutation.delete]
operations.
Write
Write(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Arguments to insert][google.spanner.v1.Mutation.insert]
,
update][google.spanner.v1.Mutation.update]
,
insert_or_update][google.spanner.v1.Mutation.insert_or_update]
, and
replace][google.spanner.v1.Mutation.replace]
operations.