4.6.1.0372

March 9, 2022

Preface

These release notes provide enhancements, changed behavior, and resolved issues. When applicable, a component-specific version number is provided for the On-Premises Connector, ODBC driver, or JDBC driver.

The product version number can be obtained from the Hybrid Data Pipeline Web UI by selecting About from the help dropdown.

The On-Premises Connector version number can be obtained by opening the On-Premises Connector Configuration Tool and clicking the Version tab.

The JDBC driver version number can be obtained (1) by calling the DatabaseMetaData.getDriverVersion() method or (2) by executing the following command from the driver installation directory:

java -cp ddhybrid.jar com.ddtek.jdbc.ddhybrid.DDHybridDriver.

For the ODBC driver, see Driver version string for details on obtaining the driver version number.

Note: For the latest data source and platform support information, refer to the Product Compatibility Guide.

Enhancements

PostgreSQL 14

Hybrid Data Pipeline now supports connectivity to PostgreSQL 14 databases. PostgreSQL 14 can also be used as a system database to store account and configuration information for a Hybrid Data Pipeline instance. This functionality is supported in the following component versions.

• Hybrid Data Pipeline Server 4.6.1.372 and higher
• On-Premises Connector 4.6.1.120 and higher

Changed Behavior

PostgreSQL call escape behavior

The default behavior for handling PostgreSQL call escape syntax has changed. Previously, Hybrid Data Pipeline only supported stored functions, and treated the non-standard escape syntax {call function()} the same as the standard escape syntax {? = call function()}. With this latest patch, Hybrid Data Pipeline supports stored functions and stored procedures for JDBC and ODBC connections. Now Hybrid Data Pipeline determines whether a function or procedure is being called based on the call escape syntax. If the return value parameter ?= is used, then the connectivity service calls a stored function. If the return value parameter is not used, then the connectivity service calls a stored procedure. You can change this default behavior by setting the CallEscapeBehavior option as an extended option under the Advanced tab. These are the valid values for the CallEscapeBehavior option:

• If set to select, treats the object being called by both the {call...} syntax and the {? = call...} syntax as a stored function and makes the applicable native call to the PostgreSQL database.
• If set to call, treats the object being called by both the {call...} syntax and the {? = call...} syntax as a stored procedure and makes the applicable native call to the PostgreSQL database.
• If set to callIfNoReturn (the default), the service determines whether to call a function or stored procedure based on the call escape syntax. If the return value parameter ?= is used, the service calls a function. If not, the service calls a stored procedure.

Resolved Issues

Issue HDP-5459 OData $expand query fails against OpenEdge data source

When using the OData $expand functionality to query an OpenEdge data source, the query failed and an error was returned.

Issue HDP-5605 SQL Editor not displaying values when two columns had the same name

When a SQL query included columns of the same name, the SQL Editor did not display the column values.

Issue HDP-5642 SQL Editor not displaying results

The SQL Editor did not display results as expected.

Known Issues

See Hybrid Data Pipeline known issues for details.