◆ getRecords() [1/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
| [in] | schema_ | Avro schema object used for decoding returned objects. |
| [in] | request_ | Request object containing the parameters for the operation. |
◆ getRecords() [2/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
◆ getRecords() [3/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
| [in] | schema_ | Avro schema object used for decoding returned objects. |
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecords() [4/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
| [in] | schema_ | Avro schema object used for decoding returned objects. |
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |
◆ getRecords() [5/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
| [in] | request_ | Request object containing the parameters for the operation. |
◆ getRecords() [6/20]
| GetRecordsResponse< boost::any > gpudb::GPUdb::getRecords | ( | const GetRecordsRequest & | request_ | ) | const |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| [in] | request_ | Request object containing the parameters for the operation. |
◆ getRecords() [7/20]
| GetRecordsResponse< boost::any > gpudb::GPUdb::getRecords | ( | const GetRecordsRequest & | request_ | ) | const |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| [in] | request_ | Request object containing the parameters for the operation. |
◆ getRecords() [8/20]
| GetRecordsResponse< boost::any > & gpudb::GPUdb::getRecords | ( | const GetRecordsRequest & | request_, |
| GetRecordsResponse< boost::any > & | response_ ) const |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
◆ getRecords() [9/20]
| GetRecordsResponse< boost::any > & gpudb::GPUdb::getRecords | ( | const GetRecordsRequest & | request_, |
| GetRecordsResponse< boost::any > & | response_ ) const |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
◆ getRecords() [10/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
◆ getRecords() [11/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecords() [12/20]
| GetRecordsResponse< boost::any > gpudb::GPUdb::getRecords | ( | const std::string & | tableName, |
| const int64_t | offset, | ||
| const int64_t | limit, | ||
| const std::map< std::string, std::string > & | options ) const |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecords() [13/20]
| GetRecordsResponse< boost::any > gpudb::GPUdb::getRecords | ( | const std::string & | tableName, |
| const int64_t | offset, | ||
| const int64_t | limit, | ||
| const std::map< std::string, std::string > & | options ) const |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecords() [14/20]
| GetRecordsResponse< boost::any > & gpudb::GPUdb::getRecords | ( | const std::string & | tableName, |
| const int64_t | offset, | ||
| const int64_t | limit, | ||
| const std::map< std::string, std::string > & | options, | ||
| GetRecordsResponse< boost::any > & | response_ ) const |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |
◆ getRecords() [15/20]
| GetRecordsResponse< boost::any > & gpudb::GPUdb::getRecords | ( | const std::string & | tableName, |
| const int64_t | offset, | ||
| const int64_t | limit, | ||
| const std::map< std::string, std::string > & | options, | ||
| GetRecordsResponse< boost::any > & | response_ ) const |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |
◆ getRecords() [16/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |
◆ getRecords() [17/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
◆ getRecords() [18/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
◆ getRecords() [19/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
| [in] | type_ | Type object used for decoding returned objects. |
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecords() [20/20]
| inline |
Retrieves records from a given table, optionally filtered by an expression and/or sorted by a column.
This operation can be performed on tables and views. Records can be returned encoded as binary, json, or geojson.
This operation supports paging through the data via the offset and limit parameters. Note that when paging through a table, if the table (or the underlying table in case of a view) is updated (records are inserted, deleted or modified) the records retrieved may differ between calls based on the updates applied.
| TResponse | The type of object being retrieved. |
| [in] | type_ | Type object used for decoding returned objects. |
| [in] | tableName | Name of the table or view from which the records will be fetched, in [schema_name.]table_name format, using standard name resolution rules. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use hasMoreRecords to see if more records exist in the result to be fetched, and offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |