What's New

This section summarizes new features and functionality of TimesTen Release 18.1 that are documented in this guide, providing links into the guide for more information.

New features in Release 18.1.1.2.0

  • TimesTen Scaleout includes a new client routing API that enables C client applications to route connections to a grid element based on the key value for a hash distribution key. This feature enables the client application to connect to the element that stores the row with the specified key value, avoiding unnecessary communication between the element storing the row and the element connected to your application. For more information, see "Client routing API for TimesTen Scaleout".

New features in Release 18.1.1.1.0

  • TimesTen supports ODBC 3.51 core interface conformance.

  • To run ODBC applications that were used with previous versions of TimesTen, be aware of the following:

    • The TimesTen driver is ODBC-compliant; however, in this release, more recent ODBC header files are provided with the TimesTen installation on Linux and UNIX platforms. The result is that some API signatures in TimesTen ODBC have changed.

    • Changes were made to update some functions to be 64-bit compliant according to the ODBC 3.51 standard.

    • These and other changes may necessitate application code changes on any platform.

    Important:

    Even if none of the required code changes applies to your applications, it is recommended that you recompile and relink existing ODBC applications in TimesTen 18.1.

    See "ODBC API incompatibilities with previous versions of TimesTen" for details.

  • In the ODBC header files provided with this release, the return code SQL_NO_DATA_FOUND (meaning no more rows are returned) is defined in sqlext.h. Applications using SQL_NO_DATA_FOUND must include this file, which is included by timesten.h.

  • There are new error codes for manual retry after transient errors. TimesTen automatically resolves most transient errors (which is particularly important for TimesTen Scaleout), but if your application detects certain error codes, it is suggested to retry the current transaction or most recent API call, as applicable. Refer to "Retrying after transient errors (ODBC)" and "Transient errors (OCI)" for details.