Progress DataDirect for JDBC for Google Analytics 4
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:
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.000428
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
FEATURES
Progress DataDirect for JDBC for Denodo Driver
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:
Version 6.0.0
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: July 3, 2024
Features
- The driver supports SQL read-write access to the Denodo Data Virtualization platform.
- The driver supports JDBC core functions. For details, refer to JDBC support in the Progress DataDirect for JDBC Drivers Reference.
- The driver supports user ID and password authentication. Refer to Authentication for details.
- The driver supports executing create, read, update, and delete (CRUD) operations on wrapper tables.
- The driver supports TLS/SSL encryption. Refer to Data encryption for details.
- The driver provides failover support. Refer to Failover for details.
- The driver provides proxy support. Refer to Proxy server for details.
Progress DataDirect for JDBC for SAP S/4HANA Driver
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:
Version 6.0.1
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.1.001709 - The driver has been enhanced to support SAP BW/4HANA and other SAP ODATA V2 services exposed through the SAP Gateway. Refer to Supported SQL statements and extensions for details.
- The driver has been enhanced to support CDS views that require parameters. Refer to CDS views for details.
- The driver has been enhanced to support HTTP Header authentication for use with the S/4HANA sandbox hosted at https://api.sap.com. Refer to HTTP header authentication (S/4HANA only).
- The driver has been enhanced to support a default value of 100000 and maximum value of 1000000 for the connection property WSFetchSize. Refer to WSFetchSize for details.
- The driver has been enhanced to set the maximum size of VARCHAR columns within the result set metadata using the MaxVarcharSize connection property. Refer to MaxVarcharSize for details.
- 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 HostName connection property has been renamed ServerName. To support existing configurations, HostName will continue to be supported as an alias for ServerName. Refer to ServerName for details.
Version 6.0.0
Features
- Supports SQL read-write access to SAP S/4HANA cloud data source
- Supports JDBC core functions
- Supports the core SQL-92 grammar
- Supports SAP S/4HANA data types through data type inference
- Supports Basic authentication
- Supports SSL data encryption
- Supports connection to custom business objects and views via custom services,
including custom fields added through SAP S/4HANA UI.
- Supports the handling of large result sets with paging and the FetchSize connection property
- Includes Interactive SQL for JDBC (JDBCISQL). It 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.
- Includes the Progress DataDirect S/4HANA Configuration Manager for quick configuration and testing of your driver in a web browser. The tool allows you to:
- Generate and edit connection URLs
- Test connect connection URLs
- Execute SQL commands for testing
- Access connection property descriptions and the full product documentation
Progress DataDirect for JDBC for SAP HANA Driver
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:
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.000879
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
Features
- Supports SQL read-write access to SAP HANA
- Supports all JDBC core functions. Refer to JDBC support in the Progress DataDirect for JDBC Drivers Reference.
- Supports the core SQL-92 grammar
- Supports SAP HANA data types. Refer to Data types and getTypeInfo() for details.
- Supports user ID and password authentication method with SCRAM-SHA-256 mechanism authentication. Refer to Authentication for details.
- Supports TLS/SSL data encryption. See Connection property descriptions for details.
- Supports proxy connections with a proxy server. See Proxy server for details.
- Supports the handling of large result sets with paging and the FetchSize connection property. Refer to FetchSize for details.
- Includes Interactive SQL. It 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. Refer to Interactive SQL for JDBC (JDBCISQL) for details.
- The installer program supports Azul Zulu JRE 11. The installer supports the
following operating systems:
- UNIX/Linux - Any operating system on a machine using a JRE that is Java SE 8 or higher (LTS version), including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
- Windows - Windows 8.1 or higher and Windows Server 2012 RC2 or higher
Important: These changes do not affect the operating system requirements of the driver.
Progress DataDirect Connect for JDBC for Sybase
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:
Version 5.1.4
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 | 5.1.4.000161 - 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 CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability. Refer to CryptoProtocolVersion for details.
- Support for result set holdability has been added to the driver.
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 driver has been enhanced to support Sybase Extended Password Encryption, which uses the asymmetrical key type, instead of the symmetrical key type. This provides stronger password encryption for the secure transmission of public key passwords
over networks.
- 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. Refer to RegisterStatementPoolMonitorMBean for details.*
Version 5.1.1
ENHANCEMENTS
- Enhanced to throw warning when EnableBulkLoad fails
- Enhanced AuthenticationMethod connection property to allow for the driver to
send a user ID in clear text and an encrypted password to the server for
authentication.
Progress DataDirect for JDBC for Oracle Service Cloud
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:
Version 5.1.4
ENHANCEMENTS
- 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.* - Support for result set holdability has been added to the driver.
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: July 3, 2024
- 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. Refer to RegisterStatementPoolMonitorMBean for details.*
Version 5.1.3
GA Release Features
- Supports SQL read-only access to data managed by Oracle Service Cloud
- Maps the Oracle Service Cloud data model to a set of relational tables and uses a client-side data cache for improved performance
- Supports the Oracle RightNow CX API
- Supports SSL encryption
- Supports statement pooling
- Supports connecting through a proxy server
Progress DataDirect for JDBC for Oracle Sales Cloud
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:
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.001065 - 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 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.*
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
Features
- Supports SQL read access to Oracle Sales Cloud
- Supports JDBC core functions
- Supports Oracle Sales Cloud data types
- Supports HTTP proxy
- Supports timeout functionality
Progress DataDirect for JDBC for Jira Driver
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:
Version 6.0.0
Enhancements
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: July 3, 2024
Features
- Supports SQL read-only access to Atlassian Jira. 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 standard JSON data types and additional data types through data type inference. Refer to Data types and getTypeInfo() for details.
- Supports Jira custom fields, including many fields added through third-party plug-ins
- Supports the handling of large result sets with configurable paging and the FetchSize and WSFetchSize connection properties. Refer to FetchSize and WSFetchSize for details.
Progress DataDirect for JDBC for Greenplum
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:
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.001535 - The driver has been enhanced to support the TLSv1.3 cryptographic protocol.
You can configure the cryptographic protocols used by the driver using the
CryptoProtocolVersion connection property. The TLSv1.3 protocol requires
Java SE 11 or higher. For details, refer to CryptoProtocolVersion.*
Available: 11/22/2024|6.0.0.001535 - The driver has been enhanced to support the following types of data types:
- Geometric types
- Network address types
- Monetary types
- Date/time types
- Range types
For details, refer to Data types.
- The driver has been enhanced to support the TXID_SNAPSHOT data type. For details, refer to 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. - 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 a customized version of the Greenplum COPY command. It provides an additional keyword, LOCALFILE, to allow you to copy data from or to standard file-system files that are stored anywhere on your network, not
just on the database server. For details, refer to Using COPY command.
- The PrepareThreshold connection property has been added to the driver. This property determines the number of PreparedStatement executions that must occur before the driver begins using server-side prepared statements. For details, refer to PrepareThreshold.
- Support for the Kerberos authentication protocol has been added with the following connection properties: AuthenticationMethod and ServicePrincipalName. For details, refer to AuthenticationMethod and ServicePrincipalName.
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: July 3, 2024
- The driver does no longer supports access to Pivotal HAWQ.
- The default value for the SupportsCatalogs connection property has been changed to true. For details, refer to SupportsCatalogs.
- 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. For details, refer to RegisterStatementPoolMonitorMBean.
Version 5.1.4
ENHANCEMENTS
- The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
- Support for result set holdability has been added to the driver.
Version 5.1.2
ENHANCEMENTS
- Added SSL support for Greenplum 4.2, incorporating eight additional connection properties
- Added SupportsCatalogs connection property, which enables driver support for catalog calls
- Added four connection properties to handle VARCHAR, LONGVARCHAR, and NUMERIC data types: MaxVarcharSize, MaxLongVarcharSize, MaxNumericPrecision, and MaxNumericScale
Version 5.1.1
GA Release Features
- Supports SQL access to Greenplum
- Supports connection pooling
- Supports the DataDirect Bulk Load API
- Includes the TransactionErrorBehavior connection property which determines how the driver handles errors that occur within a transaction
- Includes the LoginTimeout connection property which allows you to specify the amount of time the driver waits for a connection to be established before timing out the connection request
Progress DataDirect Connect XE for JDBC for Apache Impala
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:
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.001119 - The driver has been enhanced to support user impersonation with Kerberos authentication using the new ImpersonateUser connection property. Refer to the ImpersonateUser property for more information.
- The driver has been enhanced to support the Array data type through data type inference. For details, refer to Data Types.
- The driver has been enhanced to support proxy server connections. Refer to the Proxy server for more information.
- The driver has been enhanced to support LDAP authentication with user ID and password. Refer to the User ID and password authentication for more information.
- The driver supports Kerberos authentication. Refer to the Kerberos authentication for more information.
- The driver supports "No authentication," which allows you to connect without any authentication credentials. Refer to the No authentication for more information.
CHANGED BEHAVIOR
- The driver has been updated to remove all sensitive values from the string
returned by calling getURL(). You might be impacted if your applications or
tests expect these values when calling the function.*
Available: 12/xx/2024 - 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 default authentication method used by the driver has been updated to user ID/password via LDAP authentication (AuthenticationMethod=userIdPassword). See User ID and password authentication for details.
Version 5.1.4
ENHANCEMENTS
- 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 SSL data encryption. Refer to the readme for more information.*
- The driver has been enhanced to support the Char and Vachar data type with
Impala 2.1 and higher. For details, refer to Data Types. - Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
- 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. For details, refer to RegisterStatementPoolMonitorMBean.*
Version 5.1.3
GA Release Features
- Supports SQL read-write access to Cloudera Impala
- Includes the TransactionMode connection property which allows you to configure the driver to report that it supports transactions, even though Hive does not support transactions. This provides a workaround for applications which do not operate with
a driver that reports transactions are not supported.
- Support for connection pooling
Progress DataDirect for JDBC for Amazon Redshift
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:
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.001321 - The driver has been enhanced to support stored procedures.
- 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. For details, refer to CallEscapeBehavior. - The driver has been enhanced to support the following data types:
- Text maps to LONGVARCHAR
- Time maps to TIMESTAMP
- Time with time zone maps to TIMESTAMP
- Timestamp with time zone maps to TIMESTAMP
For details, refer to Data types.
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
Version 5.1.4
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.*
- 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 BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting
and provides substantial performance gains when performing batch inserts.
- The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
- Support for result set holdability has been added to the driver.
Changed Behavior
- 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.*
Version 5.1.3
GA Release Features
- Support for Amazon Redshift API
- Support for advanced security features, including SSL data encryption
- Support for connection pooling
- Support for configurable connection failover protection
- Includes the LoginTimeout connection property which allows you to specify the amount of time the driver waits for a connection to be established before timing out the connection request
- Includes the TransactionMode connection property which allows you to configure the driver to report that it supports transactions, even though Hive does not support transactions. This provides a workaround for applications which do not operate with
a driver that reports transactions are not supported.
- The driver provides support for the following standard SQL functionality:
- Create Table and Create View
- Insert
- Drop Table and Drop View
- Batches in HiveServer2 connections
Progress DataDirect for JDBC for PostgreSQL Driver
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:
Version 6.0.0
ENHANCEMENTS
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 default value for the SupportsCatalogs connection property has been changed to true. Refer to SupportsCatalogs for details.
Version 5.1.4
ENHANCEMENTS
- The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
- Support for result set holdability has been added to the driver.
Version 5.1.2
ENHANCEMENTS
- Added SupportsCatalogs connection property, which enables driver support for catalog calls
- Added four connection properties to handle VARCHAR, LONGVARCHAR, and NUMERIC data types: MaxVarcharSize, MaxLongVarcharSize, MaxNumericPrecision, and MaxNumericScale
Version 5.1.1
GA Release Features
- Supports SQL access to PostgreSQL
- Supports SSL protocol for sending encrypted data
- Supports connection pooling
- Supports the DataDirect Bulk Load API
- Includes the TransactionErrorBehavior connection property which determines how the driver handles errors that occur within a transaction
- Includes the LoginTimeout connection property which allows you to specify the amount of time the driver waits for a connection to be established before timing out the connection request
Progress DataDirect Connect for JDBC for MySQL
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:
Version 5.1.4
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 | 5.1.4.000330 - 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 CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability. Refer to CryptoProtocolVersion for details.
- Support for result set holdability has been added to the driver.
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
- 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. Refer to RegisterStatementPoolMonitorMBean for details.*
Version 5.1.1
No new features
Progress DataDirect for JDBC for Microsoft Dynamics 365 JDBC Driver
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:
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.002957 - The driver has been enhanced to support fetching data from all the companies to which the user has access. Earlier, it supported fetching data only from the default company of the user. You can configure this functionality using the new CrossCompany
connection property. Refer to CrossCompany for details.*
Available: 6.0.0.002159
- The driver has been enhanced to allow you to configure whether requests to web services timeout when the service is unresponsive. You can configure this functionality using the new WSTimeout connection property.*
- 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 allow you to configure whether requests to web services timeout when the service is unresponsive. You can configure this functionality using the new WSTimeout connection property. Refer to WSTimeout for details.
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 connection properties.*
FEATURES
Progress DataDirect for JDBC for HubSpot Driver
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:
Version 6.0.0
Enhancements
- 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: July 3, 2024
Features
Progress DataDirect for JDBC for GitHub Driver
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:
Version 6.0.0
Enhancements
- 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 Bearer token authentication. Refer to Bearer token authentication for details.*
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: July 3, 2024
- The default value of the AuthenticationMethod connection property has been changed to BearerToken.*
FEATURES
Progress DataDirect for JDBC for Apache Cassandra
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:
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.000680 - The driver has been enhanced to connect using secure connect bundles, which contain security certificates and credentials for your database. You can configure your driver to use secure connect bundles by specifying the location of the .zip file using
the new SecureConnectBundle property. For details, refer to SecureConnectBundle.*
Note that secure connect bundles are only supported by certain databases, such as DataStax Enterprise running in IBM Cloud. Refer to your database documentation for support information. - 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 the Duration data type, which maps to the Varchar JDBC type. Currently, the Duration type is supported only in simple columns, and not in Collection types. For details, refer to Data Types.*
- The driver has been enhanced to support all the data consistency levels for read and write operations that are supported by Apache Cassandra data stores. Data consistency levels are configured using the ReadConsistency and WriteConsistency connection
properties. For details, refer to ReadConsistency and WriteConsistency.*
- The driver has been enhanced to support SSL data encryption. For details, refer to Configuring SSL Encryption.*
- The driver has been enhanced to support Kerberos authentication. For details, refer to Configuring the Driver for Kerberos Authentication.*
- The driver has been enhanced to support Cassandra's tunable consistency functionality with the ReadConsistency and WriteConsistency connection
properties. For details, refer to ReadConsistency and WriteConsistency.* - The driver has been enhanced to improve the handling of large result sets and
reduce the likelihood of out-of-memory errors through the introduction of the
FetchSize, NativeFetchSize, and ResultMemorySize connection properties. For details, refer to Connection Property Descriptions.*
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
GA Release Features
- Supports SQL read-write access to Apache Cassandra
- Generates a normalized view of Cassandra data. Tuple and user-defined types are flattened into a relational parent table, while collection types are mapped as relational child tables.
- Supports Native and Refresh escape sequences to embed CQL commands in SQL-92 statements.
- Includes the TransactionMode connection property which allows you to configure the driver to report that it supports transactions, even though Cassandra does not support transactions. This provides a workaround for applications that do not operate
with a driver that reports transactions are not supported.
- Support for Binary Large Objects (BLOBs)
- Support for connection pooling
- Support for statement pooling
- Includes the LoginTimeout connection property which allows you to specify how long the driver waits for a connection to be established before timing out the connection request.
Progress DataDirect for JDBC for TeamCity
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:
ENHANCEMENTS
- The installer program has been enhanced to support Azul Zulu JRE 11. As a result of this change, the installer has ended support for some of the old operating systems. The installer supports the following operating systems after the enhancement:*
- UNIX/Linux:
- Any operating system on a machine using a JRE that is Java SE 8 or higher (LTS version), including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
- Windows:
- Windows 8.1 or higher
- Windows Server 2012 RC2 or higher
Important: These changes do not affect the operating system requirements of the driver.
- 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 fetching of multiple requests simultaneously with the ReadAhead connection property. When enabled, this connection property improves throughput and performance. Refer to ReadAhead for details. *
Version 6.0.0
FEATURES
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.
Refer to the following resources for additional information:
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.002957 - The InValuesLimit connection property has been added to the driver. It determines the maximum number of values in an IN clause subquery to be materialized. If this value is exceeded, the driver processes the subquery as a JOIN clause. You can use this property if your query exceeds the maximum SOQL length set by Salesforce. Refer to InValuesLimit for details.*
- The driver has been enhanced to support the JSON web token (JWT) grant in OAuth 2.0 authentication. The connection properties JWTCertAlias, JWTCertStore, JWTCertPassword, ClaimsIssuer, and ClaimsSubject have been added to the driver.*
Feature details:
- Available: Driver version 6.0.0.002316
(C5325.F001946.U001044)
- Proposed by the following DataDirect Idea: https://progresssoftware.aha.io/features/DDIDEAS-2764
Refer to Configuring the driver to use OAuth 2.0 with JWT grant for details.
- 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. Refer to BulkLoadVersion and BulkLoadJobSize for details.*
- 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. Refer to ApplyToLabel 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.* - 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.* - 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
unauthorized access. Refer to Configuring OAuth 2.0 authentication for details.*
- 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
properties. Refer to Connection Property Descriptions for details.
- 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. Refer to WSPoolSize for details.
- 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. Refer to WSPoolSize for details.
- 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. Refer to Refresh Map (EXT) for details.
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 driver has been enhanced to make SOAP API calls using only internal components. In earlier versions, the driver used an external library, the CXF library, to make these calls. Note that the product package no longer includes the CXF library as
a result.*
- 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. Refer to Requirements for details.*
- The precision for the Integer data type has been changed from 10 to 9. Refer to getTypeInfo for details.*
- The NUM_PREC_RADIX value for the Double data type has been changed from 10 to 2. Refer to getTypeInfo for details.*
- 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. Refer to Data Source and Driver Classes for details.
- 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. Refer to SchemaMap for details.
- 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. Refer to CreateMap for details.
- 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
model.
Version 5.1.4
ENHANCEMENTS
- Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
- 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
No new features
Version 5.1.2
No new features
Version 5.1.1
ENHANCEMENTS
- Enhanced to throw warning when EnableBulkLoad fails
Version 5.1.0
ENHANCEMENTS
- 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.
Progress DataDirect for JDBC for Oracle Eloqua
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:
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.001222 - 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 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. Refer to SpyAttributes 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.*
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
Features
- Supports SQL read-write access to Oracle Eloqua. Refer to Supported SQL functionality for details.
- Supports JDBC core functions. Refer to JDBC Support in the Progress DataDirect for JDBC Drivers Reference.
- Supports Oracle Eloqua data types. Refer to Data types and getTypeInfo() for details.
- Supports HTTP proxy. Refer to Proxy server support support for details.
- Uses a combination of REST and Bulk APIs for optimized fetch operations. Refer to Bulk operations for details.
- Supports retrieving LONGVARCHAR data, using JDBC methods designed for Character Large Object (CLOB) data. Refer to Large object (LOB) support for details.
- Supports timeout functionality. Refer to Timeouts for details.