delete_records
- delete_records(
table_name: string,
expressions: string[],
options?: Record<string, string>,
callback?: GPUdbCallback,
): Promise<DeleteRecordsResponse>Parameters
- table_name: string
Name of the table from which to delete records, in [schema_name.]table_name format, using standard name resolution rules. Must contain the name of an existing table; not applicable to views.
- expressions: string[]
A list of the actual predicates, one for each select; format should follow the guidelines provided here. Specifying one or more
expressionsis mutually exclusive to specifying record_id in theoptions. Optionaloptions: Record<string, string>Optional parameters.
Optionalcallback: GPUdbCallbackOptional callback function
Returns Promise<DeleteRecordsResponse>
Promise<Types.DeleteRecordsResponse> - Promise resolving to the response
- Defined in src/GPUdb.ts:7659
- table_name: string
delete_records_request
- delete_records_request(
request: DeleteRecordsRequest,
callback?: GPUdbCallback,
): Promise<DeleteRecordsResponse>Deletes record(s) matching the provided criteria from the given table. The record selection criteria can either be one or more
expressions(matching multiple records), a single record identified by record_id options, or all records when using delete_all_records. Note that the three selection criteria are mutually exclusive. This operation cannot be run on a view. The operation is synchronous meaning that a response will not be available until the request is completely processed and all the matching records are deleted.Parameters
- request: DeleteRecordsRequest
Request object containing the parameters for the operation
Optionalcallback: GPUdbCallbackOptional callback function
Returns Promise<DeleteRecordsResponse>
Promise<Types.DeleteRecordsResponse> - Promise resolving to the response
- Defined in src/GPUdb.ts:7627
- request: DeleteRecordsRequest
Deletes record(s) matching the provided criteria from the given table. The record selection criteria can either be one or more
expressions(matching multiple records), a single record identified by record_id options, or all records when using delete_all_records. Note that the three selection criteria are mutually exclusive. This operation cannot be run on a view. The operation is synchronous meaning that a response will not be available until the request is completely processed and all the matching records are deleted.