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

Enhancements

• The driver has been enhanced to comply with FIPS standards for data encryption. As part of this enhancement, the driver was tested with FIPS 140-3 enabled using a Red Hat OpenJDK 21 on a Red Hat Universal Base Image 9 instance. Refer to FIPS (Federal Information Processing Standard) for details.*
  Available: 1/31/2025 | 6.0.0.001477
• The driver has been enhanced to use proxy server settings defined in the JVM system properties by default. If no proxy settings are defined in the connection string or data source, the driver will attempt to use the values of the http.proxyHost and http.proxyPort JVM system properties to connect to the database.*

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
• The following connection properties have been removed from the driver: ConnectionRetryCount, ConnectionRetryDelay, LoginTimeout, and QueryTimeout. Refer to Connection property descriptions for a list of supported properties.*
• The following properties have been moved from the Advanced tab to the Performance tab on the Configuration Manager: RegisterStatementPoolMonitorMBean, StatementCallLimit, and StatementCallLimitBehavior.*

NOTES, KNOWN ISSUES, and LIMITATIONS

• JTA Support: JDBC distributed transactions through JTA are not supported.
• 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. Additional information on driver support for the JDBC API can be found in the "JDBC Support" section of the product user's guide.
  • The DataDirect for JDBC drivers allow 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.
  • 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 DataDirect for JDBC drivers support 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

• Supports SQL read-write access to Microsoft SharePoint lists. Refer to Supported SQL statements and extensions for details.
  
• Supports JDBC core functions. Refer to JDBC support in the Progress DataDirect for JDBC Drivers Reference.
  
• Supports the core SQL-92 grammar
  
• Supports SharePoint data types through data type inference. Refer to Data types, getTypeInfo(), and Introduction to the SharePoint List data model.
  
• Supports OAuth 2.0 authentication. Refer to OAuth 2.0 authentication for details.
  
• Supports the handling of large result sets with paging and the FetchSize connection property. Refer to FetchSize for details.
  
• Supports optimizing insert, update, and delete operations with the BatchUpdateChunkSize connection property. Refer to BatchUpdateChunkSize for details.
  
• Includes the DataDirect JDBC Driver Configuration Manager for quick configuration and testing of your driver. This tool allows you to:
  • Generate and edit connection URLs
  • Test connect connection URLs
  • Execute SQL commands for testing
  • Fetch OAuth tokens without using your application
  • Access connection property descriptions and the full product documentation

  Refer to Generating connection URLs with the Configuration Manager for details.