Snap Pack History: MySQL
|
|
|
Updates |
|---|---|---|---|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed the invalid fetch size error in the MySQL Select and MySQL Execute Snaps when using MariaDB accounts with custom JDBC URLs and MariaDB driver versions 2.x and 3.x. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the MySQL Insert Snap where the JOOQ library did not properly interpret the subclasses of the GEOMETRY data type when using the MariaDB driver. |
|
|
|
Improved the error messages for MySQL Snaps, where a table value is required but null values exist. |
|
|
|
Enhanced the MySQL Database Account and MySQL Dynamic Account with Custom JDBC URL field that allows you to define multi-host JDBC connection string that enables you to use multi-host URLs in a single execution. Also, you can now provide a JDBC URL in any format permitted by MySQL or MariaDB.
Note: Currently, the MySQL Snap Pack does not fully support MariaDB version 3.x, and some use cases may not function as expected. If you need to use version 3.x, we recommend that you use the JDBC Snap Pack. |
|
|
|
Reverted the MySQL patch deployed as part of 441patches31457 (query transformation change) to maintain backward compatibility. If you are using 441patches31457 patch in your MySQL pipelines, we highly recommend that you consume the latest patch 441patches31607. |
|
|
|
Fixed an issue with the MySQL Execute Snap that added newline characters in output column names when using multiline COALESCE queries during execution. |
|
|
|
Fixed an issue with the MySQL Bulk Load Snap that displayed an error "data not sufficient" when the input lacked data for AUTO_INCREMENT or DEFAULT NULL columns. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue in the MySQL Execute Snap 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 MySQL 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 the MySQL Bulk Load Snap that failed to display an exception when inserting null values into non-null columns. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the MySQL Multi Execute Snap and the MySQL Execute Snaps that displayed a null pointer exception when the Snap did not check null table metadata. |
|
|
|
Updated the Delete Condition (Truncates a Table if empty) field in the MySQL Delete Snap to Delete condition (deletes all records from a table if left blank) to indicate that all entries will be deleted from the table when this field is blank, but no truncate operation is performed. |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
The MySQL Execute Snap now includes a new Query type field. When Auto is selected, the Snap tries to determine the query type automatically. |
|
|
|
Upgraded with the latest SnapLogic Platform release. |
|
|
|
Fixed an issue with the preview data of the MySQL Execute Snap that displayed the date format as %m %d %Y (without the forward slash '/'). The Snap now displays the date as intended in %m/%d/%Y format after validation. |
|
|
|
Upgraded with the latest SnapLogic Platform release. |
|
|
|
The MySQL Insert Snap no longer includes the Preserve case-sensitivity checkbox because the database is case-insensitive. The database stores the data regardless of whether the columns in the target table and the input data are in mixed, lower, or upper case. |
|
|
|
The MySQL Insert Snap now creates the target table only from the table metadata of the second input view when the following conditions are met:
|
|
|
|
The MySQL Select Snap now works as expected when the table name is dependent on an upstream input. |
|
|
|
The following issues are fixed in the MySQL Bulk Load Snap:
|
|
|
|
Upgraded with the latest SnapLogic Platform release. |
|
|
|
Upgraded with the latest SnapLogic Platform release. |
|
|
|
Updated the label for Delete Condition to Delete Condition (Truncates Table if empty) in the MySQL Delete Snap. |
|
|
|
|