Support and certification

Visit the following web pages for the latest support and certification information.

Changes since 5.1.4 Release

  • Driver Enhancements
    • The driver has been enhanced to support connecting to a proxy server through an HTTP connection. HTTP proxy support is configurable with the new ProxyHost, ProxyPassword, ProxyPort, and ProxyUser connection properties.

    • 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 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. See SpyAttributes for details.

  • Changed Behavior

    • Java SE 7 has reached the end of its product life cycle and will no longer receive generally available security updates. As a result, the drivers will no longer support JVMs that are version Java SE 7 or earlier. Support for distributed versions of Java SE 7 and earlier will also end, including IBM SDK (Java Edition).

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

Changes for 5.1.4 Release

  • BatchMechanism Connection Property: The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to MultiRowInsert, you enable the driver to use a parameterized multi-row insert statement to execute batch inserts. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts. For additional information, see BatchMechanism.
  • CryptoProtocolVersion Connection Property: To avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability, CryptoProtocolVersion can be used with the driver. For additional information, see CryptoProtocolVersion.
  • Result Set Holdability: Support for result set holdability has been added to the driver.

Highlights of 5.1.3 Release

The driver supports:

  • Amazon Redshift API, version 2012-12-01 and later.
  • JDBC Core functionality.
  • Core SQL-92 grammar.
  • DataDirect Connection Pooling.
  • SSL data encryption.
  • Configurable connection failover protection.