An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  

Version 6.0.0

Changed Behavior

• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.*
  Note: This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  Available: 7/3/2024

NOTES, KNOWN ISSUES, and LIMITATIONS

• No Support for Connections to the JDBC Port: The driver only supports connections to the PostgreSQL-compliant socket port for Denodo (ODBC Port). The driver does not support connections to the Denodo protocol socket (JDBC port).
• Enabling Manual Transaction Mode: For the ODBC port (9996), the manual transaction mode is disabled by default. To enable it, in the database settings, set com.denodo.vdb.vdbinterface.server.odbc.ignoreTransactions=false. Note: Even after enabling the manual transaction mode, the Create operation will not work when executing transactions.
• Inserting a Value into the Column of Timestamptz Data Type: When the driver attempts to insert a value into the column of the Timestamptz data type, the time zone of the value gets converted into the time zone of the server.
• Using Bulk Load: If the driver returns the error "The specified connection object is not valid for creation of a bulk load object" while you are attempting to use the DataDirect Bulk Load API, ensure that denodo.jar is listed before any other DataDirect drivers on your classpath.
• Executing DataDirect Shell Script: For UNIX/Linux users: If you receive an error message when executing any DataDirect for JDBC shell script, make sure that the file has EXECUTE permission. To do this, use the chmod command. For example, to grant EXECUTE permission to the testforjdbc.sh file, change to the directory containing testforjdbc.sh and enter: chmod +x testforjdbc.sh
• JDBC Methods: The following notes on JDBC methods apply generally to Progress DataDirect for JDBC drivers.
  • The driver allows PreparedStatement.setXXX methods and ResultSet.getXXX methods on Blob/Clob data types, in addition to the functionality described in the JDBC specification. The supported conversions typically are the same as those for LONGVARBINARY/LONGVARCHAR, except where limited by database support.
  • Calling CallableStatement.registerOutputParameter(parameterIndex, sqlType) with sqlType Types.NUMERIC or Types.DECIMAL sets the scale of the output parameter to zero (0). According to the JDBC specification, calling CallableStatement.registerOutputParameter(parameterIndex, sqlType, scale) is the recommended method for registering NUMERIC or DECIMAL output parameters.
  • When attempting to create an updatable, scroll-sensitive result set for a query that contains an expression as one of the columns, the driver cannot satisfy the scroll-sensitive request. The driver downgrades the type of the result returned to scroll-insensitive.
  • The driver supports retrieval of output parameters from a stored procedure before all result sets and/or update counts have been completely processed. When CallableStatement.getXXX is called, result sets and update counts that have not yet been processed by the application are discarded to make the output parameter data available. Warnings are generated when results are discarded.
  • The preferred method for executing a stored procedure that generates result sets and update counts is using CallableStatement.execute(). If multiple results are generated using executeUpdate, the first update count is returned. Any result sets prior to the first update count are discarded. If multiple results are generated using executeQuery, the first result set is returned. Any update counts prior to the first result set are discarded. Warnings are generated when result sets or update counts are discarded.
  • The ResultSet methods getTimestamp(), getDate(), and getTime() return references to mutable objects. If the object reference returned from any of these methods is modified, re-fetching the column using the same method returns the modified value. The value is only modified in memory; the database value is not modified.

Features

• The driver supports SQL read-write access to the Denodo Data Virtualization platform.
  
• The driver supports JDBC core functions. For details, refer to JDBC support in the Progress DataDirect for JDBC Drivers Reference.
• The driver supports user ID and password authentication. Refer to Authentication for details.
• The driver supports executing create, read, update, and delete (CRUD) operations on wrapper tables.
• The driver supports TLS/SSL encryption. Refer to Data encryption for details.
• The driver provides failover support. Refer to Failover for details.
• The driver provides proxy support. Refer to Proxy server for details.