◆ executeSqlRaw() [1/2]
| RawExecuteSqlResponse gpudb::GPUdb::executeSqlRaw | ( | const ExecuteSqlRequest & | request_ | ) | const |
Execute a SQL statement (query, DML, or DDL).
See SQL Support for the complete set of supported SQL commands.
When a caller wants all the results from a large query (e.g., more than max_get_records_size records), they can make multiple calls to this endpoint using the offset and limit parameters to page through the results. Normally, this will execute the statement query each time. To avoid re-executing the query each time and to keep the results in the same order, the caller should specify a paging_table name to hold the results of the query between calls and specify the paging_table on subsequent calls. When this is done, the caller should clear the paging table and any other tables in the result_table_list (both returned in the response) when they are done paging through the results. pagingTable (and result_table_list) will be empty if no paging table was created (e.g., when all the query results were returned in the first call).
| [in] | request_ | Request object containing the parameters for the operation. |
◆ executeSqlRaw() [2/2]
| RawExecuteSqlResponse & gpudb::GPUdb::executeSqlRaw | ( | const ExecuteSqlRequest & | request_, |
| RawExecuteSqlResponse & | response_ ) const |
Execute a SQL statement (query, DML, or DDL).
See SQL Support for the complete set of supported SQL commands.
When a caller wants all the results from a large query (e.g., more than max_get_records_size records), they can make multiple calls to this endpoint using the offset and limit parameters to page through the results. Normally, this will execute the statement query each time. To avoid re-executing the query each time and to keep the results in the same order, the caller should specify a paging_table name to hold the results of the query between calls and specify the paging_table on subsequent calls. When this is done, the caller should clear the paging table and any other tables in the result_table_list (both returned in the response) when they are done paging through the results. pagingTable (and result_table_list) will be empty if no paging table was created (e.g., when all the query results were returned in the first call).