NuoDB JDBC Driver Release Notes

V24.2.2

  • Implemented methods linked to SQL national character types. (13680)

  • prepareCall did not succeed because required DDL statements were not synchronized.

  • Added a new VECTOR(<dimensions>, DOUBLE) data type to store vector data, such as embeddings, along with built-in functions for comparing vector similarity. For more information, see SQL Vector Type and SQL Vector Functions and Operators.

    The VECTOR data type uses the custom type code NuoDBTypes.VECTOR_DOUBLE and is fetched using the Java double[] type. The data type is set using setObject(<parameterNr>, double[], NuoDBTypes.VECTOR_DOUBLE).

  • The data types Bytes, Binary, Variable Binary were incorrectly mapped. These types now represent the appropriate JDBC types BINARY and VARBINARY.

V24.2.1

  • The options to configure connection properties when connecting to NuoDB database are now case-insensitive.

  • When a column contains a BLOB with invalid UTF-8 data, calling getString() on that column could return inaccurate results.
    The issue has been resolved. Now it reports an error message

  • nuosql could report inaccurate results when timezone is configured using timezone instead of the TimeZone connection property. (14577)
    The issue has been resolved.

  • Removed the dependency on nodeID.

V24.2.0

  • Constructing a NuoDB BLOB object from an empty java.sql.Blob object could report a SQL exception. (13675)
    The issue has been resolved.

  • Constructing a NuoDB CLOB object from an empty java.sql.Clob object could report a SQL exception. (13675)
    The issue has been resolved.

  • Added support for PEM-formatted trust certificates.

V24.1.2

  • Implemented the cancel() method for Statement and PreparedStatement interfaces. This method enables the caller to terminate a query currently executing on the NuoDB server. The method will not perform any operation if the statement it is called on is not executing a query. (8212)

  • When ResultSet.getString() was used to read the date value from a database, and the timezone configured for the connection differs from the system timezone, the JDBC driver could return inaccurate results. (13858)
    The issue has been resolved.