Database Connector Release Notes - Mule 4
Support Category: Select
Anypoint Connector for Database (Database Connector) enables you to connect to relational databases through the JDBC API.
1.13.8
October 4, 2022
Fixed Issues
Issue | ID |
---|---|
The XA Bitronix configuration pool no longer throws |
W-11743085 |
The Store procedure operation no longer returns an issue with a CLOB output while using a local transaction. |
W-11721963 |
The warn message at attempting to override property no longer have the braces with number ({0}.{1}..) displayed. |
W-11755478 |
The MuleRuntimeException shown during resolving query will show the stack trace now. |
W-11762357 |
1.13.3
May 26, 2022
Fixed Issues
Issue | ID |
---|---|
Database Connector no longer needs Oracle’s UDT scheme appended on the type name when you define the scheme on the connector’s global configuration Column types field or in the Parameter types section of the Stored procedure operation. Now, the connector searches the type name correctly. |
W-11002486 |
1.13.2
May 12, 2022
Fixed Issues
Issue | ID |
---|---|
Database Connector did not log enough information when the Connection Factory caught an exception during the connection creation. Now, the connector logs the proper stack trace with the error level. |
W-10718271 |
Database Connector no longer throws a |
W-10911002 |
1.13.0
April 11, 2022
Fixed Issues
Issue | ID |
---|---|
To fix concurrency issues that occur when using the |
W-10673234 |
1.12.0
February 4, 2022
Fixed Issues
Issue | ID |
---|---|
Support Oracle features even if the database connection is provided as a Spring bean reference to a DataSource or as a Generic Connection. |
DBCON-329 |
Access Oracle’s proprietary |
DBCON-352 |
Added synchronization while invoking createArray functions to prevent deadlocks that occurred under high concurrency. |
DBCLI-15 |
1.11.0
December 22, 2021
Fixed Issues
Issue | ID |
---|---|
The Database Connector Select operation closed the connection at the end of the flow when its result contained a LOB stream. Now the consumption of the LOB streams is tracked, and the connection is closed when there are no more LOB streams to consume or at the end of the flow. |
DBCON-304 |
Timeouts are now rounded up to whole seconds. Because timeouts are set in seconds (JDBC API), the connector rounds up values smaller than a second to avoid waiting indefinitely. |
DBCON-318 |
When using JDBC’s REF_CURSOR type as a stored procedure |
DBCON-319 |
1.10.3
July 28, 2021
Fixed Issues
-
Database Connector threw an incorrect
QueryExecutionException
exception when theSQLException
thrown by the driver didn’t have an SQLState nor a message related to the connection. Therefore, the reconnection strategy was not triggered. The correct throw message isDB:CONNECTIVITY
. (DBCLI-11)
1.10.2
July 19, 2021
Fixed Issues
-
Database Connector threw an
Invalid column type
message when using Oracle’s XMLTYPE as input for the Stored Procedure operation. The connector now manages the correct type. (DBCON-278) -
Database Connector threw an incorrect
TransactionException
exception when the connection was lost during an XA transaction. Therefore, the reconnection strategy was not triggered. The correct throw message isDB:CONNECTIVITY
. (DBCLI-7) -
The Database Connector Stored Procedure operation incorrectly executed database functions with an IN OUT parameter. Now, the operation performs correctly. (DBCLI-8)
-
Database Connector did not log enough information when the Connection Factory caught an exception during the connection creation. Now, the connector logs the proper information. (DBCLI-9)
1.10.0
June 04, 2021
Features
Added new options for Pooling profile configuration:
-
The Test connection on checkout field enables you to disable connection testing on checkout in order to improve the connector’s performance.
-
The Max statement field enables you to define the total number of
PreparedStatements
a DataSource will cache.
1.9.2
March 22, 2021
Fixed Issues
-
Database Connector threw an incorrect
NoSuchElementException
Java exception for a connection reset while iterating a result, and produced anoncatch
by thetry catch
block. The correct throw message isDB:CONNECTIVITY
. (DBCON-253) -
The Stored Procedure operation threw a
MULE:UNKONWN
error (with aNullPointerException
message) when returning an empty array. (DBCON-255) -
Database Connector closed the connection after reading the entire ResultSet of a Select operation despite having the LOB stream still open. This behavior prevented the LOB values from being read after the connection closure. (DBCON-256)
1.8.0
April 24, 2020
Features
Database Connector now accepts SQL Casting PostgreSQL and Snowflake syntax’s, through the double colon (::) expression. For example, SELECT MAX(modified_date)::DATE FROM sales
, where modified_date
is of type string. This feature does not change the existing behavior for the connector (MULE-18150).
Fixed Issues
-
MySQL driver now logs to the Mule Log when using MySQL Driver 8.x and higher (MULE-18287).
-
Fixed issue that prevented the usage of the BulkInsert Operation within a ForEach scope (MULE-18260).
-
Fixed issue that prevented the logging of information about a BulkUpdate Operation when an Exception was thrown by it (MULE-18290).
1.7.0
March 13, 2020
Features
You can now specify additional pooling profile properties using the additional-properties tab for any Database provider. This feature allows you to specify only additional properties and not to override the main ones (like maxPoolSize) if they were already specified.
Fixed Issues
Fixed issue where oracle DB connector was unable to use specific pooling profile configurations (such as checkoutTimeout
or idleConnectionTestPeriod
). (MULE-17949)
Fixed issue where first stored procedure calls to database took a long time. (MULE-17808)
Fixed issue where operation stored-procedure did not offer the parameter to configure repeatable streaming. (MULE-17898)
1.5.2
April 16, 2019
Fixed Issues
-
Errors while transforming to JSON the output of Oracle SP call with custom types. (MULE-16589)
-
Can’t get parameter data types when store procedure name includes schema. (MULE-16685)
-
FlowListener callback retains too much state. (MULE-16366)
-
Errors when using Oracle’s UDT Table type. (MULE-16401)
-
Database connector not sending value of the IN-OUT parameter. (MULE-16484)
-
"Unable to convert between" error when using SP in MsSql. (MULE-16339)
1.4.0
August 7, 2018
Features
-
Now in Generic Connections, the username and password can be configured outside the JDBC URL for improved security and support for multitenancy.
-
Improved New Row trigger, now hints with the available tables to retrieve rows.
-
Support for PostgreSQL type casting.
Fixed Issues
-
Database On New Row listener should provide a hint to available tables. (MULE-15310)
-
Database Connector uses deprecated DriverClass when using new MySQL Drivers. (MULE-15218)
-
Database Connector doesn’t support PostgreSQL type casting. (MULE-15101)
1.3.4
June 29, 2018
Features
-
Fixed issue that prevented inserting and updating CLOB types in Oracle Databases.
-
When using the newest MySQL Driver, the connector uses the new preferred Driver Class instead of the old deprecated one.
-
Fixed issue when consuming CLOB and BLOB types when using Derby databases.
Fixed Issues
-
Database Connector should automatically transform CLOB types on Oracle Databases. (MULE-15240)
-
Database Connector uses deprecated DriverClass when using new MySQL Drivers. (MULE-15218)
1.3.1
March 16, 2018
Features
This release includes the following enhancements, changes, and fixes:
-
Now the Oracle Connection can be configured with a Service Name.
-
When doing a Select now the output metadata communicates correctly if the columns values can be have a null value or not.
-
In some scenarios when an error occurs the connection string with embedded credentials could be logged.