PostgreSQL - Update
This page is no longer maintained (May 13, 2026). For the most current information, go to PostgreSQL - Update
On this page
Snap type: | Write | |||||||
|---|---|---|---|---|---|---|---|---|
Description: | This Snap executes a SQL update with the given properties. Keys from the document will be used as the columns to update and their values will be the updated value in the column. Updates will be batched up until the account's batch size property or until the structure of the update statement changes. An update statement will change if an incoming document contains different keys than a previous document. | |||||||
Prerequisites: | None | |||||||
Support: | Works in Ultra Tasks. | |||||||
Limitations: | If you want to filter by vector values, you must query vector columns using String format in the Where clause. | |||||||
Account: | This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Configuring PostgreSQL Accounts for information on setting up this type of account. | |||||||
Views: |
| |||||||
Settings | ||||||||
Label | Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | |||||||
Schema name
| The database schema name. Selecting a schema filters the Table name list to show only those tables within the selected schema. The property is suggestible and will retrieve available database schemas during suggest values. The values can be passed using the pipeline parameters but not the upstream parameter. Example: myschema Default value: [None] | |||||||
Table name | Required. The name of the table to execute the update operation on. The values can be passed using the pipeline parameters but not the upstream parameter. Example: people Default value: [None] | |||||||
Update condition
| Required. Specify the SQL WHERE clause of the update statement. You can define specific values or columns to update (Set condition) in the upstream Snap, such as Mapper Snap, and then use the WHERE clause to apply these conditions on the columns sourced from the upstream Snap. For instance, here is a sample of an Update SQL query:
If the Update Condition field is left blank, the condition is applied on all the records of the target table. In a scenario where the downstream Snap depends on the data processed in an Upstream Database Bulk Load Snap, use the Script Snap to add delay for the data to be available. Refer to the example to understand how to use the Update Condition. Examples: Without using expressions
Using expressions
Caution Using expressions that join strings together to create SQL queries or conditions has a potential SQL injection risk and is hence unsafe. Ensure that you understand all implications and risks involved before using concatenation of strings with '=' Expression enabled. Default value: [None] | |||||||
Number of retries | Specifies the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response. Example: 3 Default value: 0 | |||||||
Retry interval (seconds) | Specifies the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. Example: 10 Default value: 1 | |||||||
Select one of the three modes in which the Snap executes. Available options are:
Default Value: Execute only | ||||||||