Snap Pack history: JDBC
|
|
|
Updates |
|---|---|---|---|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the Generic JDBC - Select Snap that caused a failure when connecting to the Teradata database. Improved the output for the CLOB data type when used with the SELECT statement in the Generic JDBC - Execute Snap. This update has resulted in the following behavior change: Behavior change: Previously, the output for a Teradata object displayed as shown below: "col_clob": "com.teradata.jdbc.jdk6.JDK6_SQL_Clob@2f8e6bdd" With 442patches32366, the output now reflects the actual content inserted, as shown below: "col_clob": "This is a CLOB text" |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the Generic JDBC - Execute Snap (main29887) where DATETIME fields from Informix were returned as formatted strings instead of Timestamp objects, causing inconsistency across environments. The Snap now correctly returns Timestamp objects, restoring behavior to match pre-jOOQ upgrade versions and ensures consistent datetime formatting and timezone handling across all environments. |
|
|
|
Fixed an issue in the Generic JDBC - Execute Snaps where using an alias for a DATETIME field caused an unintended UTC value to be appended to the output when connecting to a MySQL database. |
|
|
|
|
|
|
|
Fixed the Null Pointer Exception (NPE) issue in the JDBC Snaps. Now, these Snaps display an exception error instead of NPE when the URL properties (key and value) and either key or value are empty. |
|
|
|
Fixed an issue with Generic JDBC - Select , Generic JDBC - Execute , and Generic JDBC - Insert Snaps that failed with class not found error for geometry and geography data types when connecting to the SQL server. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Warning: Breaking change:
With the
Note:
Behavior change:
Earlier, the ROWID columns were displayed in binary
(Base64 encoded data) form in the output. With the
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
The
JDBC Snap Pack
version
438patches28052, which removed the default bundled Oracle and
Redshift drivers (JAR files), is now rolled back with
438patches28541. Now, the drivers are bundled by default with the
Oracle Snap Pack and Redshift Snap Pack. This rollback might cause a
connectivity issue when connecting the JDBC Snaps to the Sybase database using the
jConnect Driver. Based on your use case requirements, follow the
below steps: |
|
|
|
Fixed a connectivity issue with the Generic JDBC Snaps that resulted in an
error when attempting to connect the JDBC account to a Sybase database using the
jConnect driver.Note:
Breaking change: Your existing pipelines that use JDBC Snaps to integrate with Oracle or Redshift databases using the bundled Oracle or Redshift JDBC drivers will stop functioning with the 438patches28052. Workaround You must manually upload the Oracle or Redshift JDBC driver in the JDBC Database account to run your pipelines successfully. Download the drivers: OJDBC: Maven Repository: com.oracle.database.jdbc » ojdbc6 » 11.2.0.4 Redshift: Maven Repository: com.amazon.redshift » redshift-jdbc42 » 2.1.0.11 |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the Generic JDBC - Insert Snap that exposed sensitive information in the error message when the batch operation was not successful. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
Added the following new Snaps to the
JDBC Snap Pack
:
|
|
|
|
The database connection error message in the Generic JDBC Database Account is improved for clarity and readability. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
The Generic JDBC Database Account now supports the SSH Tunneling connection. You can now encrypt the network connection between your client and the database server, ensuring a highly secure connection. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
The Generic JDBC Database Account previously took a longer time to execute and was aborted after a few minutes, which affected the performance of the Snap. The Snap's performance is optimized now and takes lesser time for execution. |
|
|
|
The Generic JDBC Snaps connecting to the DB2 database now take lesser time to execute thereby improving the performance. |
|
|
|
Enhanced the Generic JDBC Database Account Support dynamic values for Account, Advanced, and URL properties. |
|
|
|
|
|
|
|
Enhanced the Generic JDBC Database Account in the JDBC Snap Pack to include Netsuite as an option for the Database name field to connect to the NetSuite database. While configuring the account, if you select Netsuite or Autodetect (if the Snap detects the target database as NetSuite) then the Limit rows field in the Generic JDBC - Select Snap is ignored. |
|
|
|
Enhanced the following Snaps to support DML (Data Manipulation Language) operations (CREATE, ALTER, INSERT, and SELECT) when using AWS Athena database. |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixes the Pipeline execution failure issue when using the JDBC Snaps with a Microsoft Access account by setting the correct quotation handler for the configured account. |
|
|
|
Enhances the Generic JDBC - Select Snap to return only the fields (provided in the Output Fields) in the output schema (second output view), through a new check box Fetch Output Fields In Schema. If the Output Fields property is empty all the columns are visible. |