The following Snaps The PostgreSQL Select Snap now work as expected when the table name is dependent on an upstream input:

.

Enhanced the PostgreSQL Account and PostgreSQL Dynamic Account with SSH Tunneling configurations to encrypt the network connection between the client and the PostgreSQL Database server, thereby ensuring a secure network connection.

4.29

main15993

14 May 2022 

Stable

Upgraded with the latest SnapLogic Platform release.

Fixed an issue with PostgreSQL - Execute Snap, where the Snap failed when using Delete query with the RETURNING function.

Enhanced the PostgreSQL - Execute Snap to invoke stored procedures.

Enhanced the performance of PostgreSQL - Bulk Load Snap significantly. SnapLogic anticipates that the Snap will execute up to 3 times faster than the previous version for enterprise workloads.

Enhanced the PostgreSQL - Select Snap to return only the selected output fields or columns in the output schema (second output view) using the Fetch Output Fields In Schema check box. If the Output Fields field is empty all the columns are visible. 

4.22 Patch

Fixed the PostgreSQL - Bulk Load Snap by preventing it from adding extra double quotes when loading values from input documents.

Fixed the issue where Snowflake SCD2 Snap generates two output documents despite no changes to Cause-historization fields with DATE, TIME and TIMESTAMP Snowflake data types, and with Ignore unchanged rows field selected.

4.21 Patch

Fixed the following issues with DB Snaps:

• The connection thread waits indefinitely causing the subsequent connection requests to become unresponsive.
• Connection leaks occur during Pipeline execution.

4.21 Patch

Fixed the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends. 

Fixed an issue with the PostgreSQL - Update Snap wherein the Snap is unable to perform operations when:

• An expression is used in the Update condition property.
• Input data contain the character '?'.

Added new Snap PostgresSQL Bulk Load.

Fixed an issue with the PostgreSQL grammar to better handle the single quote characters.

Fixed an issue with tables sharing an overlapping column name wherein Pipeline execution fails due to the table collision.

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

• Fixed an issue with the PostgreSQL Execute Snap wherein the Snap would send the input document to the output view even if the Pass through field is not selected in the Snap configuration. With this fix, the Snap sends the input document to the output view, under the key original, only if you select the Pass through field.
• Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.

Fixed an issue with the Lookup Snap passing data simultaneously to output and error views when some values contained spaces at the end.

Replaced Max idle time and Idle connection test period properties with Max life time and Idle Timeout properties respectively, in the Account configuration. The new properties fix the connection release issues that were occurring due to default/restricted DB Account settings.

Added support for Amazon Aurora and Azure SQL DB.

snapsmrc486

Provided an interim fix for an issue with the PostgreSQL 10 accounts by re-registering the driver for each account validation. The final fix is being shipped in a separate build.

4.12 Patch

Updated the driver from version 8.4.704 to version 9.4.1207 to support PostgreSQL v10 servers.

snapsmrc480

4.11 Patch 

PostgreSQL Snap Pack - Fixed an issue when inserting a valid NaN value into a column.

Previously the Postgres PGObject datatype could not be serialized. It is now handled as a String.

snapsmrc414

Added Auto commit property to the Select and Execute Snaps at the Snap level to support overriding of the Auto commit property at the Account level.

PostgreSQL Execute: New Snap advanced property Auto commit has been implemented to fix the Select query error in PostgreSQL replica servers.

4.9 Patch

Fixed an issue regarding connection not closed after login failure; Expose autocommit for "Select into" statement in PostgreSQL Execute Snap and Redshift Execute Snap.

Potential fix for JDBC deadlock issue.

4.8.0 Patch

Fixed PostgreSQL Snap Pack rendering dates that are one hour off from the date returned by database query for non-UTC Snaplexes.

4.8.0 Patch

22 Feb 2017 

Addressed an issue where some changes made in the platform patch MRC294 to improve perfomance caused Snaps in the listed Snap Packs to fail.

snapsmrc398

• Info tab added to accounts.
• Database accounts now invalidate connection pools if account properties are modified and login attempts fail.

Fixed an issue for database Select Snaps regarding Limit rows not supporting an empty string from a pipeline parameter.

4.7.0 Patch

Resolved an issue with the PostgreSQL Execute Snap failing with a “java.util.regex.Pattern” error.

snapsmrc382

postgres1584

• Resolved an issue in the PostgreSQL - Execute Snap that resulted from restrictions on the 'with' operator in conjunction with an 'insert' statement.

• Resolved an issue in the PostgreSQL Snaps that resulting from restrictions on the 'with' operator in conjunction with the RECURSIVE keyword.

• Resolved an issue with PostgreSQL Select Snap not parsing JSON data type correctly.
• Note: The fix for this issue required updating libraries that impacted all database Snaps except those for MongoDB.

This Snap Pack is now compatible with the PostgreSQL drivers available in 4.3 Patch mrc222.

• PostgreSQL Insert Snap: resolved an issue where it inserts a negative value when the input data was out of range.
• PostgreSQL Snaps did not properly handle when a table name was created in mixed case.
• JSON paths in WHERE clauses should be processed as bind values after the expression is evaluated.

• A - otd:6828 Postgres Snap shows wrong data type in preview for timestamp withtime zone data type
• Dynamic DB queries now supported in the Execute Snap.
• The SQL statement property now can be set as an expression property. When it is an expression, it will be evaluated with each input document and one SQL statement per each input document will be executed.
• Known issue: When the SQL statement property is an expression, the pipeline parameters are shown in the suggest, but not the input schema.
• With the SQL statement property set as an expression, the Snap can be exposed to SQL injection. Please use this feature with caution.

• PostgreSQL Insert: Enhanced data type support.
• PostgreSQL Lookup: bug fixes on lookup failures; Pass-though on no lookup match property added to allow you to pass the input document through to the output view when there is no lookup matching.
  • PostgreSQL Select Snap: added support for handling array types.