You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: A comment for field ranges in message .google.spanner.v1.KeySet is changed (#2407)
* docs: A comment for field `ranges` in message `.google.spanner.v1.KeySet` is changed
docs: A comment for message `Mutation` is changed
docs: A comment for field `columns` in message `.google.spanner.v1.Mutation` is changed
docs: A comment for field `values` in message `.google.spanner.v1.Mutation` is changed
docs: A comment for field `key_set` in message `.google.spanner.v1.Mutation` is changed
docs: A comment for field `insert_or_update` in message `.google.spanner.v1.Mutation` is changed
docs: A comment for field `replace` in message `.google.spanner.v1.Mutation` is changed
docs: A comment for message `PlanNode` is changed
docs: A comment for enum `Kind` is changed
docs: A comment for field `variable` in message `.google.spanner.v1.PlanNode` is changed
docs: A comment for field `index` in message `.google.spanner.v1.PlanNode` is changed
docs: A comment for field `kind` in message `.google.spanner.v1.PlanNode` is changed
docs: A comment for field `short_representation` in message `.google.spanner.v1.PlanNode` is changed
docs: A comment for field `plan_nodes` in message `.google.spanner.v1.QueryPlan` is changed
docs: A comment for method `CreateSession` in service `Spanner` is changed
docs: A comment for method `GetSession` in service `Spanner` is changed
docs: A comment for method `DeleteSession` in service `Spanner` is changed
docs: A comment for method `ExecuteSql` in service `Spanner` is changed
docs: A comment for method `ExecuteStreamingSql` in service `Spanner` is changed
docs: A comment for method `Read` in service `Spanner` is changed
docs: A comment for method `Commit` in service `Spanner` is changed
docs: A comment for method `Rollback` in service `Spanner` is changed
docs: A comment for method `PartitionQuery` in service `Spanner` is changed
docs: A comment for method `PartitionRead` in service `Spanner` is changed
docs: A comment for method `BatchWrite` in service `Spanner` is changed
docs: A comment for field `session_template` in message `.google.spanner.v1.BatchCreateSessionsRequest` is changed
docs: A comment for field `session_count` in message `.google.spanner.v1.BatchCreateSessionsRequest` is changed
docs: A comment for field `approximate_last_use_time` in message `.google.spanner.v1.Session` is changed
docs: A comment for field `multiplexed` in message `.google.spanner.v1.Session` is changed
docs: A comment for enum `Priority` is changed
docs: A comment for field `request_tag` in message `.google.spanner.v1.RequestOptions` is changed
docs: A comment for field `transaction_tag` in message `.google.spanner.v1.RequestOptions` is changed
docs: A comment for message `DirectedReadOptions` is changed
docs: A comment for message `DirectedReadOptions` is changed
docs: A comment for message `DirectedReadOptions` is changed
docs: A comment for field `location` in message `.google.spanner.v1.DirectedReadOptions` is changed
docs: A comment for field `auto_failover_disabled` in message `.google.spanner.v1.DirectedReadOptions` is changed
docs: A comment for field `include_replicas` in message `.google.spanner.v1.DirectedReadOptions` is changed
docs: A comment for field `exclude_replicas` in message `.google.spanner.v1.DirectedReadOptions` is changed
docs: A comment for enum value `PROFILE` in enum `QueryMode` is changed
docs: A comment for field `optimizer_version` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `optimizer_statistics_package` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `transaction` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `params` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `param_types` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `partition_token` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `seqno` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `data_boost_enabled` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `last_statement` in message `.google.spanner.v1.ExecuteSqlRequest` is changed
docs: A comment for field `params` in message `.google.spanner.v1.ExecuteBatchDmlRequest` is changed
docs: A comment for field `param_types` in message `.google.spanner.v1.ExecuteBatchDmlRequest` is changed
docs: A comment for field `seqno` in message `.google.spanner.v1.ExecuteBatchDmlRequest` is changed
docs: A comment for field `last_statements` in message `.google.spanner.v1.ExecuteBatchDmlRequest` is changed
docs: A comment for field `precommit_token` in message `.google.spanner.v1.ExecuteBatchDmlResponse` is changed
docs: A comment for message `PartitionOptions` is changed
docs: A comment for field `partition_size_bytes` in message `.google.spanner.v1.PartitionOptions` is changed
docs: A comment for field `max_partitions` in message `.google.spanner.v1.PartitionOptions` is changed
docs: A comment for field `transaction` in message `.google.spanner.v1.PartitionQueryRequest` is changed
docs: A comment for field `sql` in message `.google.spanner.v1.PartitionQueryRequest` is changed
docs: A comment for field `params` in message `.google.spanner.v1.PartitionQueryRequest` is changed
docs: A comment for field `param_types` in message `.google.spanner.v1.PartitionQueryRequest` is changed
docs: A comment for field `key_set` in message `.google.spanner.v1.PartitionReadRequest` is changed
docs: A comment for field `partition_token` in message `.google.spanner.v1.Partition` is changed
docs: A comment for enum value `ORDER_BY_UNSPECIFIED` in enum `OrderBy` is changed
docs: A comment for enum value `ORDER_BY_PRIMARY_KEY` in enum `OrderBy` is changed
docs: A comment for enum value `LOCK_HINT_UNSPECIFIED` in enum `LockHint` is changed
docs: A comment for enum value `LOCK_HINT_EXCLUSIVE` in enum `LockHint` is changed
docs: A comment for field `key_set` in message `.google.spanner.v1.ReadRequest` is changed
docs: A comment for field `limit` in message `.google.spanner.v1.ReadRequest` is changed
docs: A comment for field `partition_token` in message `.google.spanner.v1.ReadRequest` is changed
docs: A comment for field `data_boost_enabled` in message `.google.spanner.v1.ReadRequest` is changed
docs: A comment for field `order_by` in message `.google.spanner.v1.ReadRequest` is changed
docs: A comment for field `request_options` in message `.google.spanner.v1.BeginTransactionRequest` is changed
docs: A comment for field `mutation_key` in message `.google.spanner.v1.BeginTransactionRequest` is changed
docs: A comment for field `single_use_transaction` in message `.google.spanner.v1.CommitRequest` is changed
docs: A comment for field `return_commit_stats` in message `.google.spanner.v1.CommitRequest` is changed
docs: A comment for field `max_commit_delay` in message `.google.spanner.v1.CommitRequest` is changed
docs: A comment for field `precommit_token` in message `.google.spanner.v1.CommitRequest` is changed
docs: A comment for field `exclude_txn_from_change_streams` in message `.google.spanner.v1.BatchWriteRequest` is changed
docs: A comment for enum value `SERIALIZABLE` in enum `IsolationLevel` is changed
PiperOrigin-RevId: 800749899
Source-Link: googleapis/googleapis@39c8072
Source-Link: googleapis/googleapis-gen@42cfcdb
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiNDJjZmNkYmJhYjFjYmUxMmY0ZTA5Njg5NTkxZjlkZmYwNjlmMDg3ZSJ9
* 🦉 Updates from OwlBot post-processor
See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md
---------
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
// 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
35
+
// Arguments to [insert][google.spanner.v1.Mutation.insert],
36
+
// [update][google.spanner.v1.Mutation.update],
37
+
// [insert_or_update][google.spanner.v1.Mutation.insert_or_update], and
// already exist, the transaction fails with error `NOT_FOUND`.
81
86
Writeupdate=2;
82
87
83
-
// Like [insert][google.spanner.v1.Mutation.insert], except that if the row already exists, then
84
-
// its column values are overwritten with the ones provided. Any
85
-
// column values not explicitly written are preserved.
88
+
// Like [insert][google.spanner.v1.Mutation.insert], except that if the row
89
+
// already exists, then its column values are overwritten with the ones
90
+
// provided. Any column values not explicitly written are preserved.
86
91
//
87
-
// When using [insert_or_update][google.spanner.v1.Mutation.insert_or_update], just as when using [insert][google.spanner.v1.Mutation.insert], all `NOT
88
-
// NULL` columns in the table must be given a value. This holds true
89
-
// even when the row already exists and will therefore actually be updated.
92
+
// When using
93
+
// [insert_or_update][google.spanner.v1.Mutation.insert_or_update], just as
94
+
// when using [insert][google.spanner.v1.Mutation.insert], all `NOT NULL`
95
+
// columns in the table must be given a value. This holds true even when the
96
+
// row already exists and will therefore actually be updated.
90
97
Writeinsert_or_update=3;
91
98
92
-
// Like [insert][google.spanner.v1.Mutation.insert], except that if the row already exists, it is
93
-
// deleted, and the column values provided are inserted
94
-
// instead. Unlike [insert_or_update][google.spanner.v1.Mutation.insert_or_update], this means any values not
95
-
// explicitly written become `NULL`.
99
+
// Like [insert][google.spanner.v1.Mutation.insert], except that if the row
100
+
// already exists, it is deleted, and the column values provided are
101
+
// inserted instead. Unlike
102
+
// [insert_or_update][google.spanner.v1.Mutation.insert_or_update], this
103
+
// means any values not explicitly written become `NULL`.
96
104
//
97
105
// In an interleaved table, if you create the child table with the
98
106
// `ON DELETE CASCADE` annotation, then replacing a parent row
0 commit comments