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.
For a list a list of issues resolved since general availability, refer to the fixes.
Certified with Salesforce API version 55* Driver version 6.0.0.002057 (C4729.F001619.U000799)
Certified with Salesforce API version 51* Driver version 6.0.0.001413 (C3106.F001062.U000497)
Certified with Salesforce Service Cloud* Driver version 6.0.0.001251 (C2679.F000912.U000443)
Certified with Salesforce API version 49* Driver version 6.0.0.001058 (C2148.F000699.U000370)
Certified with OpenJDK 11* Driver version 6.0.0.000140 (C0158.F000174.U000090)
Certified with OpenJDK 8 on Windows and Linux* Driver version 6.0.0.000140 (C0158.F000174.U000090)
Certified with Salesforce API version 44
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.*
The driver has been enhanced to support the Salesforce Bulk API V2 for bulk load operations. This functionality can be enabled and configured using the new BulkLoadVersion and BulkLoadJobSize connection properties.*
The ApplyToLabel connection property has been added to the driver. It determines whether the driver applies the toLabel() function to the picklist fields when executing queries.*
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.*
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.*
The driver has been enhanced to support Apache CXF 3.3.4.*
yes, no, on and off have been added as valid values for the connection properties that accept boolean values.*
The driver has been enhanced to support OAuth 2.0, which is an open protocol for token-based authentication. OAuth 2.0 allows you to authenticate without specifying a user ID or password, eliminating the risk of exposing them to
The driver has been enhanced to support the Salesforce Bulk API, including PK chunking, for bulk fetch operations. This functionality can be enabled and configured with the EnableBulkFetch, BulkFetchThreshold, EnablePKChunking, and PKChunkSize connection
The driver has been enhanced to support multiple simultaneous sessions. The number of active sessions should not exceed the number permitted by your Salesforce account and can be limited by the setting of the WSPoolSize connection property.
The new WSPoolSize connection property allows you to specify the maximum number of sessions the driver uses. This allows the driver to have multiple Web service requests active simultaneously when multiple JDBC connections are open, thereby improving
throughput and performance.
The Refresh Map SQL extension has been added to the driver. REFRESH MAP discovers native objects that have been added to the native data store since connection or since the last refresh and maps the objects into your relational view of native data.
It also incorporates any configuration changes made to your relational view by reloading the schema map and associated files.
The ConfigOptions connection option has been deprecated. As a result, the driver has been enhanced to support setting each of the configuration options supported by ConfigOptions as a standalone connection option. Although the driver will continue
to support ConfigOptions until the next major release of the driver, in anticipation of this change, we recommend updating your data sources and connection URL strings to set configuration options as standalone connection options.*
The driver has been updated to require a Java Virtual Machine (JVM) that is Java SE 8 or higher, including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.*
The precision for the Integer data type has been changed from 10 to 9.*
The NUM_PREC_RADIX value for the Double data type has been changed from 10 to 2.*
The data source class com.ddtek.jdbcx.sforce.SForceDataSource40 has been deprecated. The data source class com.ddtek.jdbcx.sforce.SForceDataSource should be used for data source connections. The data source class com.ddtek.jdbcx.sforce.SForceDataSource
now supports all JDBC specifications.
In addition to the information listed here, refer to this compatibility FAQ for guidance on upgrading
from the Progress DataDirect for JDBC for Salesforce 5.1 driver to the 6.0 driver.
The driver’s SQL engine was upgraded for this release. Consequently, there are differences in how the driver handles some SQL queries. Refer to this SQL engine upgrade document for details.
The 6.0 driver pushes queries to Salesforce whenever possible. Queries that cannot be pushed to Salesforce with the 6.0 driver may be slower than comparable queries made with previous versions of the driver because data may be paged to disk while
completing an operation. If you experience slow performance, please contact Technical Support.
Bulk load operations are no longer restricted to 10,000 rows for evaluation installations of the driver.
The native CURRENCY and PERCENTAGE data types now map to the DECIMAL JDBC data type. In earlier releases, these data types mapped to the DOUBLE data type.
The DatabaseName property has been deprecated. The SchemaMap property should now be used to specify the fully qualified path of the configuration file where the map of the Salesforce data model is written.
The CreateDB and RefreshSchema properties have been deprecated. The CreateMap property should now be used to specify whether the driver creates a new schema map when establishing the connection.
The RefreshDirtyCache property has been deprecated. Now, for every fetch operation, the driver refreshes the cached object to pick up changes made to tables and rows.
The following connection properties and configuration options now have new default settings.
The default value of the EnableBulkLoad connection property has been updated to true. By default, the bulk load protocol can be used for inserts, updates, and deletes based on the BulkLoadThreshold property.
The default value for the StmtCallLimit connection property has been updated to 100. By default, the driver can make a maximum of 100 Web service calls when executing any single SQL statement or metadata query.
The default value for the AuditColumns configuration option has been updated to all (AuditColumns=all). By default, the driver includes all audit columns and the master record id column in its table definitions.
The default value for the CustomSuffix configuration option has been updated to include (CustomSuffix=include). By default, the driver includes the "__c" suffix table and column names when mapping the Salesforce data model.
The default value for the MapSystemColumnName configuration option has been updated to 0 (MapSystemColumnNames=0). By default, the driver does not change the names of the Salesforce system columns when mapping the Salesforce data
Certified with Oracle JDK 11.* Driver version 5.1.4.000226 (F000381.U000186)
Certified with OpenJDK 11.* Driver version 5.1.4.000226 (F000381.U000186)
Certified with OpenJDK 8 on Windows and Linux.* Driver version 5.1.4.000226 (F000381.U000186)
Certified with Salesforce API version 38* Driver version 5.1.4.000185 (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 5.1.4.000146, 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.*
Certified with Salesforce API versions 29
Certified with Salesforce API versions 28
Certified with Salesforce API versions 27
Enhanced to throw warning when EnableBulkLoad fails
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.