gpudb::InsertRecordsRequest< T >

Constructs an InsertRecordsRequest object with default parameters.

Definition at line 974 of file insert_records.h.

Constructs an InsertRecordsRequest object with the specified parameters.

Definition at line 1262 of file insert_records.h.

An array of binary-encoded data for the records to be added.

All records must be of the same type as that of the table. Empty array if listEncoding is json.

Definition at line 1282 of file insert_records.h.

Optional parameters.

• insert_records_update_on_existing_pk: Specifies the record collision policy for inserting into a table with a primary key. If set to true, any existing table record with primary key values that match those of a record being inserted will be replaced by that new record (the new data will be “upserted”). If set to false, any existing table record with primary key values that match those of a record being inserted will remain unchanged, while the new record will be rejected and the error handled as determined by ignore_existing_pk, allow_partial_batch, and return_individual_errors. If the specified table does not have a primary key, then this option has no effect. Supported values:
  • insert_records_true: Upsert new records when primary keys match existing records.
  • insert_records_false: Reject new records when primary keys match existing records.
  The default value is insert_records_false.
• insert_records_enable_inplace_updates: Applies only when upserting (when update_on_existing_pk is true). If set to true, an existing record matched by primary key is modified in place. If set to false, it is updated by deleting the existing record and inserting a replacement (delete and insert), which prevents the change from being reflected in dependent materialized views until they are refreshed. Supported values:
  • insert_records_true
  • insert_records_false
  The default value is insert_records_true.
• insert_records_ignore_existing_pk: Specifies the record collision error-suppression policy for inserting into a table with a primary key, only used when not in upsert mode (upsert mode is disabled when update_on_existing_pk is false). If set to true, any record being inserted that is rejected for having primary key values that match those of an existing table record will be ignored with no error generated. If false, the rejection of any record for having primary key values matching an existing record will result in an error being reported, as determined by allow_partial_batch and return_individual_errors. If the specified table does not have a primary key or if upsert mode is in effect (update_on_existing_pk is true), then this option has no effect. Supported values:
  • insert_records_true: Ignore new records whose primary key values collide with those of existing records.
  • insert_records_false: Treat as errors any new records whose primary key values collide with those of existing records.
  The default value is insert_records_false.
• insert_records_pk_conflict_predicate_higher: The record with higher value for the column resolves the primary-key insert conflict. The default value is ”.
• insert_records_pk_conflict_predicate_lower: The record with lower value for the column resolves the primary-key insert conflict. The default value is ”.
• insert_records_return_record_ids: If true then return the internal record id along for each inserted record. Supported values:
  • insert_records_true
  • insert_records_false
  The default value is insert_records_false.
• insert_records_truncate_strings: If set to true, any strings which are too long for their target charN string columns will be truncated to fit. Supported values:
  • insert_records_true
  • insert_records_false
  The default value is insert_records_false.
• insert_records_return_individual_errors: If set to true, success will always be returned, and any errors found will be included in the info map. The “bad_record_indices” entry is a comma-separated list of bad records (0-based). If so, there will also be an “error_N” entry for each record with an error, where N is the index (0-based). Supported values:
  • insert_records_true
  • insert_records_false
  The default value is insert_records_false.
• insert_records_allow_partial_batch: If set to true, all correct records will be inserted and incorrect records will be rejected and reported. Otherwise, the entire batch will be rejected if any records are incorrect. Supported values:
  • insert_records_true
  • insert_records_false
  The default value is insert_records_false.
• insert_records_dry_run: If set to true, no data will be saved and any errors will be returned. Supported values:
  • insert_records_true
  • insert_records_false
  The default value is insert_records_false.
• insert_records_request_schema_str: Type schema of data (when listEncoding is binary), in [[“column_name”,“column_type”]] format. When non-empty and different from the table’s schema, the server remaps the incoming records to the table’s full schema. Columns present in the table but absent from this schema are filled using their default values, NULL (if nullable), or an error is returned. If empty, records must match the table’s full schema. The default value is ”.
• insert_records_transformations: Comma-separated expressions, one per target table column. Each expression is evaluated per record. Empty entries (two consecutive commas) mean no transformation for that column – the value is resolved from the input record, table default, NULL, or an error. Expressions may reference input columns by name or by position ($1 for the first input column,$2 for the second, etc.). The default value is ”.

The default value is an empty map.

Definition at line 1477 of file insert_records.h.

Name of table to which the records are to be added, in [ schema_name. ]table_name format, using standard name resolution rules.

Must be an existing table.

Definition at line 1275 of file insert_records.h.