Database Connector Release Notes - Mule 4

Database Connector threw an incorrect QueryExecutionException exception when the SQLException 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 is DB:CONNECTIVITY. (DBCLI-11)

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 is DB: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)

Database Connector exported incorrect packages, now the connector exports the correct packages. (DBCON-283, DBCON-286)

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.

Database Connector logged an exception at ERROR level causing a large amount of content to be saved in the log registry. Now the connector uses the correct log level, DEBUG. (DBCLI-5)

When using the Insert operation, Database Connector didn’t correctly resolve the NCLOB types, which resulted in a DB:QUERY_EXECUTION error with an Invalid column type message. (DBCON-265)

Database Connector threw an incorrect NoSuchElementException Java exception for a connection reset while iterating a result, and produced a noncatch by the try catch block. The correct throw message is DB:CONNECTIVITY. (DBCON-253)

The Stored Procedure operation threw a MULE:UNKONWN error (with a NullPointerException 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)

Fixed an issue in which the On Table Row operation closed connections once rows were dispatched to the next processor, thus preventing the consumption of streams. (DBCON-234)

Introduced the Query single operation that enables you to select a single record from a database and access the result without any additional transformations to the payload. This operation doesn’t use streaming.

Fixed an issue in which stored procedures were not closing connections when no stream was returned, nor any transaction performed. (DBCON-225)

When the Bulk insert operation used debug output, it logged a placeholder instead of the record number. (DBCON-228)

Fixed "Struct cannot be cast to [Ljava.lang.Object" issue that prevented the connector to create SQL Arrays or Structs containing BLOBs or CLOBs types. (DBCON-190)

Fixed issue where connections were not closed if a stored procedure returned multiple result sets. (DBCON-182)

Fixed issue where dbCreateStruct performance introduced a regression since Mule 3.9.4. (DBCON-178)

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).

The issue where connection leaks occurred when using dynamic configurations is fixed. (MULE-17792)

The issue where using stored procedures with a CLOB In Out parameter failed to execute on Oracle is fixed. (MULE-17846)

Stored procedures took too long to execute with the Oracle Database. (MULE-17394)

Unable to retrieve responses with custom data types. (MULE-17470)

Unable to execute stored procedures defined within packages on an Oracle Database. (MULE-17418)

On stored procedures where the output return variable is set to null, the output should not be processed further. (MULE-16961)

db:select operation fails to throw a connectivity error. (MULE-16950)

Connector doesn’t ensure data is consumable by DataWeave if it has an encoding different from the one used by the runtime. (MULE-16460)

Clob in out parameters are not made consumable with Oracle DB. (MULE-16770)

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)

Can’t get stored procedure name from SQL query when there is whitespace before parentheses. (MULE-15793)

MySQL default driver causes a memory leak. (MULE-15748)

Database On Table Row should hint available columns for ID and Watermark using Value Providers. (MULE-15644)

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.

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)

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.

Database Connector should automatically transform CLOB types on Oracle Databases. (MULE-15240)

Database Connector uses deprecated DriverClass when using new MySQL Drivers. (MULE-15218)

SQL Server Connection provider doesn’t communicate the library RegEx. (MULE-14876)

Upgrade c3p0 to Mule fork version. (MULE-14859)

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.

Connectors doesn’t communicate correctly if their POJOs properties are nullable or not. (MULE-14701)

Credentials leak in error messages. (MULE-14740)

Add the capability of configuring the Service Name for an Oracle Connection. (MULE-14750)

Added a new message source which triggers a flow per each row in a table.

When doing a SELECT over a CLOB column the value is retrieved as a InputStream.

Create Trigger for Database. (MULE-14657)

DB Connector returns ClLOB objects instead of InputStreams. (MULE-14615)

Added out-of-the-box support for connecting to Microsoft SQL Server Databases.

Improved support for Derby sub-protocols.

Improved UX.

ColumnTypes parameter should be placed on Advanced Tab. (MULE-14515)

Add Value Providers for SubSubProtocols in Derby Connection Provider. (MULE-13921)