Issues fixed in DataDirect JDBC 6.0

When attempting to retrieve schema information, the driver failed to return results for catalogs with names containing hyphens.

When attempting to retrieve large datasets from SAP S/4HANA, the driver failed to fetch the complete result set when the server enforced server-driven paging.

The driver failed to connect to Snowflake when specifying a lowercase or case-sensitive role name with URL-encoded double quotes.

When invoking the isValid() API to validate the connection, the driver executedan incorrect query. As a result, errors were logged in the database logs.

The driver logged verbose informational and warning messages from the Apache Arrow library to the console by default.

The JDBC drivers returned a generic SQLException instead of the SQLNonTransientException when accessing closed resources.

The JDBC drivers returned a generic SQLException instead of the SQLNonTransientException when accessing closed resources.

The driver returned a generic SQLException instead of a SQLNonTransientException when accessing closed resources.

The drivers returned the generic SQLException instead of the SQLNonTransientException when accessing closed resources.

The JDBC drivers threw a generic SQLException exception instead of the SQLNonTransientException when accessing closed resources.

The driver returned a generic SQLException instead of SQLNonTransientException when accessing closed resources.

The DataDirect JDBC drivers threw the generic ‘SQLException’ instead of ‘SQLNonTransientException’ when accessing closed resources.

The driver returned a generic SQLException instead of the SQLNonTransientException when accessing closed resources.

The object closed scenario returned a generic SQLException instead of a dedicated SQLNonTransientException.

The DD JDBC drivers threw the generic ‘SQLException’ instead of ‘SQLNonTransientException’ when accessing closed resources.

Glasswall scanner reported multiple .so dependencies in the driver as malware.

Vulnerabilities found in Snowflake, Greenplum, and Google BigQuery JDBC Driver JAR files by Glasswall scanner

In a FIPS-compliant environment, the customer attempted to connect to Snowflake using the JDBC driver with key-pair authentication but encountered an error, while the native Snowflake driver functioned without any issues.

The driver failed to recognize a stored procedure when null values are passed to the UUID parameters.

When an application sent parameters in the body of a POST request for Select statements, the driver returned the first page but did not send any subsequent pages.

The driver returned a generic SQLException instead of a SQLNonTransientException when accessing closed resources.

The driver returned a “Hexadecimal string is invalid” error while fetching the Varchar data type with getBytes() method.

The driver failed to execute SELECT queries containing comments at the end and returned a 'syntax error at end of input' message.

Upgraded the driver’s BouncyCastle library to version 1.83.

When attempting to run a stored procedure, the driver threw a null pointer exception.

Connection to AstraDB using token‑based authentication failed with a null‑pointer exception when supplying Secure Connection Bundle details.

Glasswall scanner detected vulnerabilities detected in driver Jar files.

When executing boolean ret = stmt.execute();, the driver incorrectly returned false instead of the expected true.

The driver ignored the filterable=false metadata and pushed filters for non‑filterable Boolean fields to the server.

The driver returned a null CatalogName for system schemas when invoking getSchemas(connection.getCatalog(), null).

When connected to Azure Synapse, the driver returned an unsupported error message during query execution, preventing proper identification of the issue.

The connector mishandled a PATCH request to insert a child table into a third-party API.

When attempting to insert array data, the driver returned a ClassCastException error.

When running the driver in a FIPS compliant environment, the driver OCSP validation flag prevented the driver from connection.

Calling {{DatabaseMetaData.getProcedureColumns}} on a standalone stored procedure returned combined metadata from both the standalone and packaged procedures when they share the same name, instead of returning only the standalone procedure’s columns.

The driver reported differing column type names for timestamp columns based on whether the metadata originated from DatabaseMetaData or ResultSetMetaData.

When executing a getSchemas() call, the driver did not return schemas whose names were enclosed in double quotes.

When filtering endpoints that require parameters using {{INFORMATION_SCHEMA.SYSTEM_COLUMNS_REQUIRED_FILTERS}}, the required filter was not exposed in the path for the {{PROPERTIESLIST}} endpoint.

The Cassandra JDBC driver did not support the ClusterNodes connection option for specifying multiple cluster node hostnames, unlike the ODBC Cassandra driver where this option was present.

The Composer was unable to retrieve data in tabular format for an endpoint.

The driver returned an {{ORA-00910}} error when the query {{SELECT CAST('test' AS VARCHAR2(32767)) FROM dual}}  was executed in environments where Extended Data Types (EDT) were not enabled.

When attempting to connect to an LDAP server, the driver returned the "Not an instance of DirContext" error.

When invoking DatabaseMetadata.getTables, the connector did not return all the tables in the ResultSet.

When attempting to execute getFunctionColumns(), the driver did not return COLUMN_NAME for the unnamed function return types.

The JDBC API call {{setMaxRows()}} did not work correctly with the driver as compared to the expected functionality of the {{LIMIT}} clause.

The driver successfully connected to the dedicated pool in Azure Synapse Analytics. However, it encountered a StackOverflowError when attempting to connect to the serverless pool.

When using the driver, TIMESTAMP(N) columns (precision 1–12) reported a fixed scale of 6 instead of reflecting the precision defined at creation.

When attempting to execute getFunctionColumns(), the driver did not return COLUMN_NAME for the unnamed function return types.

When connecting to a partially contained database, the driver failed to retrieve metadata for stored procedures using the getProcedures catalog function.

When attempting to connect to an SSL-enabled, cloud-hosted instance, the driver returned the following error: "SCRAM channel binding check failed."

When executing a SELECT query that included the DISTINCT keyword, the driver returned incorrect results.

When attempting to fetch the object identifier for the Geometry data type, the driver returned "UNKNOWN".

The driver does not expose the QualifyNormalizedNames property. This property allows you to prefix child tables (normalized from arrays and objects) with the names of parent objects.

Connections from Linux using a UNC path to the REST file fail with the exception “An unexpected error has occurred while loading the native schema map file.”

When attempting to execute a batch operation with AutoCommit set to false, the driver encountered a BatchUpdateException and returned an incorrect value for getLargeUpdateCounts().

When attempting to execute a batch operation with AutoCommit set to false, the driver encountered a BatchUpdateException and returned an incorrect value from getLargeUpdateCounts().

The driver failed during statement compilation when executing a parameterized insert into a {{BINARY}} column.

When attempting to read a VARCHAR2 column from a table in an Oracle 19c database configured with ZHT16BIG5 as the default character set, the driver returned the following error: “Transliteration failed. Reason: Destination buffer too small or partial character encountered. ErrorCode=0, SQLState=HY000.”

Metadata APIs returned incorrect {{COLUMN_SIZE}} values for Db2z servers for the data types {{BIGINT}}, {{REAL}}, and {{DECFLOAT}}.

Metadata APIs returned incorrect {{COLUMN_SIZE}} values for Db2i servers for the data types GRAPHIC, VARGRAPHIC, NVARCHAR, DOUBLE, and REAL.

The getIndexInfo() API returned defined constraints along with indexes.

When attempting to connect to the server using NTLM authentication, the driver returned the following error: “java.lang.NoSuchMethodError”

When using the driver with Kerberos authentication, an initialization process resulted in a StackOverflowError.

When attempting to insert multiple invalid records using executeBatch(), the driver hung.

When attempting to insert multiple invalid records using executeBatch(), the driver hung.

When attempting to insert multiple invalid records using executeBatch(), the driver hung.

When attempting to insert multiple invalid records using executeBatch(), the driver hung.

An InvalidProtocolBufferException error was thrown when using the driver with version 1.9.0 of Kotlin.

The driver has been updated to remove all values that should be secured from the string returned by calling getURL().

When attempting to fetch large number of rows, the driver returned the following error: “java.lang.ArrayIndexOutOfBoundsException".

When ServerMode=1 (Server), the driver hung when attempting to connect using SQLDriverConnectW.

When calling executeBatch() for stored procedures, the driver returned a NullPointerException.

The driver returned the incorrect length for columns of the XML datatype.

When attempting to create a stored procedure with multiple SQL queries, the driver returned the following error: “Unterminated dollar-quoted string”.

The driver failed to connect to SharePoint using OAuth2.0 authentication via Oracle Gateway.

The Oracle Kerberos connection failed when the AllowWeakCrypto configuration setting was disabled.

The driver was unable to use the Google BigQuery Streaming API when executing INSERT statements containing table, dataset, or project names that included a backtick (`) character.

When calling getSchemas on a database with a database name containing a period, the driver returned an empty result set.

For SAP S4/HANA connections, the driver returned incorrect results for queries that reference a column as both the JOIN condition to another table and as a constant.

The driver returned a “General Error” error when connecting to a keyspace that contained tables with CompositeType or DynamicCompositeType columns.

The driver returned a general, non-informational error message when attempting to authenticate using the Service Account authentication by specifying an empty .json file for the Service Account Private Key connection option.

When attempting to run a SELECT * query, the driver returned the following error: “414 (URI Too Long for GET)”.