Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

RDSDataService

import { RDSDataService } from "https://aws-api.deno.dev/v0.4/services/rdsdataservice.ts?docs=full";
class RDSDataService {
constructor(apiFactory: client.ApiFactory);
async batchExecuteStatement(params: BatchExecuteStatementRequest, opts?: client.RequestOptions): Promise<BatchExecuteStatementResponse>;
async beginTransaction(params: BeginTransactionRequest, opts?: client.RequestOptions): Promise<BeginTransactionResponse>;
async commitTransaction(params: CommitTransactionRequest, opts?: client.RequestOptions): Promise<CommitTransactionResponse>;
async executeSql(params: ExecuteSqlRequest, opts?: client.RequestOptions): Promise<ExecuteSqlResponse>;
async executeStatement(params: ExecuteStatementRequest, opts?: client.RequestOptions): Promise<ExecuteStatementResponse>;
async rollbackTransaction(params: RollbackTransactionRequest, opts?: client.RequestOptions): Promise<RollbackTransactionResponse>;
 
static ApiMetadata: client.ApiMetadata;
}

§Constructors

§
new RDSDataService(apiFactory: client.ApiFactory)
[src]

§Methods

§

Runs a batch SQL statement over an array of data.

You can run bulk update and insert operations for multiple records using a DML statement with different parameter sets. Bulk operations can provide a significant performance improvement over individual insert and update operations.

Note: If a call isn't part of a transaction because it doesn't include the transactionID parameter, changes that result from the call are committed automatically. There isn't a fixed upper limit on the number of parameter sets. However, the maximum size of the HTTP request submitted through the Data API is 4 MiB. If the request exceeds this limit, the Data API returns an error and doesn't process the request. This 4-MiB limit includes the size of the HTTP headers and the JSON notation in the request. Thus, the number of parameter sets that you can include depends on a combination of factors, such as the size of the SQL statement and the size of each parameter set. The response size limit is 1 MiB. If the call returns more than 1 MiB of response data, the call is terminated.

§

Starts a SQL transaction.

Note: A transaction can run for a maximum of 24 hours. A transaction is terminated and rolled back automatically after 24 hours. A transaction times out if no calls use its transaction ID in three minutes. If a transaction times out before it's committed, it's rolled back automatically. DDL statements inside a transaction cause an implicit commit. We recommend that you run each DDL statement in a separate ExecuteStatement call with continueAfterTimeout enabled.

§

Ends a SQL transaction started with the BeginTransaction operation and commits the changes.

§

Runs one or more SQL statements.

Note: This operation is deprecated. Use the BatchExecuteStatement or ExecuteStatement operation.

§

Runs a SQL statement against a database.

Note: If a call isn't part of a transaction because it doesn't include the transactionID parameter, changes that result from the call are committed automatically. If the binary response data from the database is more than 1 MB, the call is terminated.

§

Performs a rollback of a transaction. Rolling back a transaction cancels its changes.

§Static Properties