Changes Since 6.0.0 GA

  • Driver 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. See FIPS (Federal Information Processing Standard) for details.
  • Changed Behavior
    • The connection property SpyAttributes has been updated to exclude the attribute load=classname, which was previously used to load the driver specified by the given class name. See SpyAttributes for details.

Changes for 6.0.0 Release

  • The driver provides proxy support. See Proxy server and Connection property descriptions for more information.
  • The driver has been enhanced to support the following data types:
    • Text
    • Time
    • Time with time zone
    • Timestamp with time zone
      Note: For more information, see Data types.
  • The driver has been enhanced to include timestamp in the Spy and JDBC packet logs by default. If required, you can disable the timestamp logging by specifying the following at connection: For Spy logs, set spyAttributes=(log=(file)Spy.log;timestamp=no) and for JDBC packet logs, set ddtdbg.ProtocolTraceShowTime=false.
  • The driver has been enhanced to support stored procedures for Redshift.
  • The driver supports the CallEscapeBehavior connection property. It determines whether the driver calls a user-defined function or a stored procedure when JDBC Call escape syntax is used in a SQL statement. See CallEscapeBehavior for details.
  • Interactive SQL for JDBC (JDBCISQL) is now installed with the product. JDBCISQL is a command-line interface that supports connecting your driver to a data source, executing SQL statements and retrieving results in a terminal. This tool provides a method to quickly test your drivers in an environment that does not support GUIs. See Interactive SQL for JDBC (JDBCISQL) for details.
  • The driver no longer registers the Statement Pool Monitor as a JMX MBean by default. To register the Statement Pool Monitor and manage statement pooling with standard JMX API calls, the new RegisterStatementPoolMonitorMBean connection property must be set to true.