|
class | BatchCreateRequest |
| Creates multiple new sessions. More...
|
|
class | BeginTransactionRequest |
| Begins a new transaction. This step can often be skipped: Read, ExecuteSql and Commit can begin a new transaction as a side-effect. More...
|
|
class | CommitRequest |
| Commits a transaction. The request includes the mutations to be applied to rows in the database. More...
|
|
class | CreateRequest |
| Creates a new session. A session can be used to perform transactions that read and/or modify data in a Cloud Spanner database. Sessions are meant to be reused for many consecutive transactions. More...
|
|
class | DeleteRequest |
| Ends a session, releasing server resources associated with it. This will asynchronously trigger cancellation of any operations that are running with this session. More...
|
|
class | ExecuteBatchDmlRequest |
| Executes a batch of SQL DML statements. This method allows many statements to be run with lower latency than submitting them sequentially with ExecuteSql. More...
|
|
class | ExecuteSqlRequest |
| Executes an SQL statement, returning all results in a single reply. This method cannot be used to return a result set larger than 10 MiB; if the query yields more data than that, the query fails with a FAILED_PRECONDITION error. More...
|
|
class | ExecuteStreamingSqlRequest |
| Like ExecuteSql, except returns the result set as a stream. Unlike ExecuteSql, there is no limit on the size of the returned result set. However, no individual row in the result set can exceed 100 MiB, and no column value can exceed 10 MiB. More...
|
|
class | GetRequest |
| Gets a session. Returns NOT_FOUND if the session does not exist. This is mainly useful for determining whether a session is still alive. More...
|
|
class | ListRequest |
| Lists all sessions in a given database. More...
|
|
class | PartitionQueryRequest |
| Creates a set of partition tokens that can be used to execute a query operation in parallel. Each of the returned partition tokens can be used by ExecuteStreamingSql to specify a subset of the query result to read. The same session and read-only transaction must be used by the PartitionQueryRequest used to create the partition tokens and the ExecuteSqlRequests that use the partition tokens. More...
|
|
class | PartitionReadRequest |
| Creates a set of partition tokens that can be used to execute a read operation in parallel. Each of the returned partition tokens can be used by StreamingRead to specify a subset of the read result to read. The same session and read-only transaction must be used by the PartitionReadRequest used to create the partition tokens and the ReadRequests that use the partition tokens. There are no ordering guarantees on rows returned among the returned partition tokens, or even within each individual StreamingRead call issued with a partition_token. More...
|
|
class | ReadRequest |
| Reads rows from the database using key lookups and scans, as a simple key/value style alternative to ExecuteSql. This method cannot be used to return a result set larger than 10 MiB; if the read matches more data than that, the read fails with a FAILED_PRECONDITION error. More...
|
|
class | RollbackRequest |
| Rolls back a transaction, releasing any locks it holds. It is a good idea to call this for any transaction that includes one or more Read or ExecuteSql requests and ultimately decides not to commit. More...
|
|
class | StreamingReadRequest |
| Like Read, except returns the result set as a stream. Unlike Read, there is no limit on the size of the returned result set. However, no individual row in the result set can exceed 100 MiB, and no column value can exceed 10 MiB. More...
|
|
|
| SessionsResource (Google.Apis.Services.IClientService service) |
| Constructs a new resource. More...
|
|
virtual BatchCreateRequest | BatchCreate (Google.Apis.Spanner.v1.Data.BatchCreateSessionsRequest body, string database) |
| Creates multiple new sessions. More...
|
|
virtual BeginTransactionRequest | BeginTransaction (Google.Apis.Spanner.v1.Data.BeginTransactionRequest body, string session) |
| Begins a new transaction. This step can often be skipped: Read, ExecuteSql and Commit can begin a new transaction as a side-effect. More...
|
|
virtual CommitRequest | Commit (Google.Apis.Spanner.v1.Data.CommitRequest body, string session) |
| Commits a transaction. The request includes the mutations to be applied to rows in the database. More...
|
|
virtual CreateRequest | Create (Google.Apis.Spanner.v1.Data.CreateSessionRequest body, string database) |
| Creates a new session. A session can be used to perform transactions that read and/or modify data in a Cloud Spanner database. Sessions are meant to be reused for many consecutive transactions. More...
|
|
virtual DeleteRequest | Delete (string name) |
| Ends a session, releasing server resources associated with it. This will asynchronously trigger cancellation of any operations that are running with this session. More...
|
|
virtual ExecuteBatchDmlRequest | ExecuteBatchDml (Google.Apis.Spanner.v1.Data.ExecuteBatchDmlRequest body, string session) |
| Executes a batch of SQL DML statements. This method allows many statements to be run with lower latency than submitting them sequentially with ExecuteSql. More...
|
|
virtual ExecuteSqlRequest | ExecuteSql (Google.Apis.Spanner.v1.Data.ExecuteSqlRequest body, string session) |
| Executes an SQL statement, returning all results in a single reply. This method cannot be used to return a result set larger than 10 MiB; if the query yields more data than that, the query fails with a FAILED_PRECONDITION error. More...
|
|
virtual ExecuteStreamingSqlRequest | ExecuteStreamingSql (Google.Apis.Spanner.v1.Data.ExecuteSqlRequest body, string session) |
| Like ExecuteSql, except returns the result set as a stream. Unlike ExecuteSql, there is no limit on the size of the returned result set. However, no individual row in the result set can exceed 100 MiB, and no column value can exceed 10 MiB. More...
|
|
virtual GetRequest | Get (string name) |
| Gets a session. Returns NOT_FOUND if the session does not exist. This is mainly useful for determining whether a session is still alive. More...
|
|
virtual ListRequest | List (string database) |
| Lists all sessions in a given database. More...
|
|
virtual PartitionQueryRequest | PartitionQuery (Google.Apis.Spanner.v1.Data.PartitionQueryRequest body, string session) |
| Creates a set of partition tokens that can be used to execute a query operation in parallel. Each of the returned partition tokens can be used by ExecuteStreamingSql to specify a subset of the query result to read. The same session and read-only transaction must be used by the PartitionQueryRequest used to create the partition tokens and the ExecuteSqlRequests that use the partition tokens. More...
|
|
virtual PartitionReadRequest | PartitionRead (Google.Apis.Spanner.v1.Data.PartitionReadRequest body, string session) |
| Creates a set of partition tokens that can be used to execute a read operation in parallel. Each of the returned partition tokens can be used by StreamingRead to specify a subset of the read result to read. The same session and read-only transaction must be used by the PartitionReadRequest used to create the partition tokens and the ReadRequests that use the partition tokens. There are no ordering guarantees on rows returned among the returned partition tokens, or even within each individual StreamingRead call issued with a partition_token. More...
|
|
virtual ReadRequest | Read (Google.Apis.Spanner.v1.Data.ReadRequest body, string session) |
| Reads rows from the database using key lookups and scans, as a simple key/value style alternative to ExecuteSql. This method cannot be used to return a result set larger than 10 MiB; if the read matches more data than that, the read fails with a FAILED_PRECONDITION error. More...
|
|
virtual RollbackRequest | Rollback (Google.Apis.Spanner.v1.Data.RollbackRequest body, string session) |
| Rolls back a transaction, releasing any locks it holds. It is a good idea to call this for any transaction that includes one or more Read or ExecuteSql requests and ultimately decides not to commit. More...
|
|
virtual StreamingReadRequest | StreamingRead (Google.Apis.Spanner.v1.Data.ReadRequest body, string session) |
| Like Read, except returns the result set as a stream. Unlike Read, there is no limit on the size of the returned result set. However, no individual row in the result set can exceed 100 MiB, and no column value can exceed 10 MiB. More...
|
|
The "sessions" collection of methods.
Creates a new session. A session can be used to perform transactions that read and/or modify data in a Cloud Spanner database. Sessions are meant to be reused for many consecutive transactions.
Sessions can only execute one transaction at a time. To execute multiple concurrent read-write /write-only transactions, create multiple sessions. Note that standalone reads and queries use a transaction internally, and count toward the one transaction limit.
Active sessions use additional server resources, so it is a good idea to delete idle and unneeded sessions. Aside from explicit deletes, Cloud Spanner may delete sessions for which no operations are sent for more than an hour. If a session is deleted, requests to it return NOT_FOUND
.
Idle sessions can be kept alive by sending a trivial SQL query periodically, e.g., "SELECT
1"
.
- Parameters
-
body | The body of the request. |
database | Required. The database in which the new session is created. |
Executes an SQL statement, returning all results in a single reply. This method cannot be used to return a result set larger than 10 MiB; if the query yields more data than that, the query fails with a FAILED_PRECONDITION
error.
Operations inside read-write transactions might return ABORTED
. If this occurs, the application should restart the transaction from the beginning. See Transaction for more details.
Larger result sets can be fetched in streaming fashion by calling ExecuteStreamingSql instead.
- Parameters
-
body | The body of the request. |
session | Required. The session in which the SQL query should be performed. |
Creates a set of partition tokens that can be used to execute a query operation in parallel. Each of the returned partition tokens can be used by ExecuteStreamingSql to specify a subset of the query result to read. The same session and read-only transaction must be used by the PartitionQueryRequest used to create the partition tokens and the ExecuteSqlRequests that use the partition tokens.
Partition tokens become invalid when the session used to create them is deleted, is idle for too long, begins a new transaction, or becomes too old. When any of these happen, it is not possible to resume the query, and the whole operation must be restarted from the beginning.
- Parameters
-
body | The body of the request. |
session | Required. The session used to create the partitions. |
Creates a set of partition tokens that can be used to execute a read operation in parallel. Each of the returned partition tokens can be used by StreamingRead to specify a subset of the read result to read. The same session and read-only transaction must be used by the PartitionReadRequest used to create the partition tokens and the ReadRequests that use the partition tokens. There are no ordering guarantees on rows returned among the returned partition tokens, or even within each individual StreamingRead call issued with a partition_token.
Partition tokens become invalid when the session used to create them is deleted, is idle for too long, begins a new transaction, or becomes too old. When any of these happen, it is not possible to resume the read, and the whole operation must be restarted from the beginning.
- Parameters
-
body | The body of the request. |
session | Required. The session used to create the partitions. |
Reads rows from the database using key lookups and scans, as a simple key/value style alternative to ExecuteSql. This method cannot be used to return a result set larger than 10 MiB; if the read matches more data than that, the read fails with a FAILED_PRECONDITION
error.
Reads inside read-write transactions might return ABORTED
. If this occurs, the application should restart the transaction from the beginning. See Transaction for more details.
Larger result sets can be yielded in streaming fashion by calling StreamingRead instead.
- Parameters
-
body | The body of the request. |
session | Required. The session in which the read should be performed. |