Progress DataDirect Connect XE for JDBC for Salesforce

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

Version 5.1.4

  • Certified with Salesforce API version 38*
    Driver version (C0242.F000319.U000137) 
  • Certified with Salesforce API versions 33 and 34*
  • The Salesforce driver has been updated to require a Java SE 7 or higher JVM to comply with revisions to Salesforce security standards. Beginning June 25th, 2016, Salesforce is deprecating support for the TLS 1.0 encryption protocol for inbound and outbound connections. TLS 1.0 is initially being disabled for Sandbox instances before being retired for all instances in early 2017. To maintain compatibility with Salesforce services, the driver must use a JVM that allows TLS 1.0 to be disabled independently of other encryption protocols. This functionality is available with Java SE 7 and higher. Therefore, Java SE 7 or higher must be installed on your system and the JVM must be defined on your system path to use the driver and Salesforce services. Beginning with build, the driver will return an error if you attempt to connect using a Java SE 6 or earlier JVM. For more information on the Salesforce disablement of TLS 1.0, refer to Salesforce disabling TLS 1.0 - Salesforce Knowledge Article 000221207.*
  • Support for result set holdability has been added to the driver.
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement Pool Monitor and manage statement pooling with standard JMX API calls.*

Version 5.1.3

  • Certified with Salesforce API versions 29

Version 5.1.2

  • Certified with Salesforce API versions 28

Version 5.1.1

  • Certified with Salesforce API versions 27
  • Enhanced to throw warning when EnableBulkLoad fails

Version 5.1.0

  • Certified with Salesforce API versions 26
  • The new KeywordConflictSuffix keyword=value pair for the ConfigOptions property allows you to specify a string that the driver appends to any object or field name that conflicts with a SQL engine keyword. For example, if you specify KeywordConflictSuffix=TAB, the driver maps the Case object in Salesforce to CASETAB.
  • The new RefreshSchema connection property specifies whether the driver automatically refreshes the remote object mapping and other information contained in a remote schema the first time a user connects to an embedded database.


Read Next

What's new