8 TERADATA

============================================================================= Simba Teradata ODBC Driver with SQL Connector Release Notes =============================================================================

The release notes provide details of enhancements, features, and known issues in Simba Teradata ODBC Driver 16.20.00.0006, as well as the version history.

16.20.00.0006 ================================================================

Released 2017-10-12

Enhancements & New Features

  • Help button in driver dialog box

    You can now click the Help button in the driver dialog box on Windows and macOS to open an HTML version of the driver documentation.

  • Updated handling for expired passwords on Windows

    When connecting using the SQLDriverConnect function, if the password is expired, the driver can now open a dialog box that prompts you to update your password. This dialog box does not open if DriverCompletion is set to SQL_NO_PROMPT.

  • Improved workflows for using user-defined character sets

    User-defined character sets are now easier to set up and use:

    • You no longer need to configure user-defined character sets on the server side. Also, if you send data to or receive data from a Latin table, the driver now automatically converts the encoding base on the application code page to the appropriate character set.
    • You no longer need to specify a translation DLL. If no translation DLL is specified, the driver converts characters based on the current application code page.

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 16.20.00.0006.

  • When converting data from SQL_C_CHARACTER to SQL_NUMERIC, if the value contains leading or trailing spaces, the driver returns a 40550 error (“Invalid character value for cast specification”) instead of ignoring the spaces and completing the conversion successfully.

  • When calling SQLColAttribute to retrieve the SQL_COLUMN_CHARACTER_SET value for a CHAR or VARCHAR column, the driver always returns 0 (Charset Undefined) in the last argument instead of the actual value.

  • In some cases, when working with DateTime data, the driver returns a “Protocol deserialization failed” error.

  • When the driver is configured to work in ANSI mode (the Session Mode option or SessionMode property is set to ANSI), changes in the database cannot be rolled back as expected.

  • In some cases, the translation DLL files do not work as expected, and the output text is incorrect.

  • When working with the ODBC Data Source Administrator on Windows, if the Session Character Set option (the CharacterSet property) is set to a character set that is activated in dbc.CharTranslationsV, the DSN cannot be saved.

  • Driver fails to access tables with names that contain underscore characters (_).

  • When converting data from SQL_DECIMAL to a character type, the driver truncates all trailing zeroes (0).

    This issue has been resolved. The driver now only truncates trailing zeroes if the buffer is not large enough to contain the value with the trailing zeroes.

  • In some cases, when creating a table that contains AVRO or BINARY data, the operation fails due to an error in how the length of the data is calculated.

  • When inserting SLOB data, some insertions might fail due to a miscalculation of the buffer size.

  • On UNIX machines, the driver fails to detect and use the system locale when returning error messages.

  • On Linux machines, when SQLExtendedFetch is called on SQL_NUMERIC data, the data is truncated unexpectedly.

    This issue has been resolved. The problem occurred because the UseRegionalSettings property, which should only be applicable on Windows and macOS machines, was being applied to Linux connections.

  • On ODBC 2.x connections, the driver sometimes converts data incorrectly when converting from SQL_TD_FLOATING_NUBMER or SQL_BIGINT to SQL_C_DEFAULT.

  • In some cases, when converting data from a String type to a Float type, the driver does not return the expected value even if the value can be represented precisely as a Double.

Known Issues The following are known issues that you may encounter due to limitations in the data source, the driver, or an application.

  • Some custom fields not supported for SQLGetDescField

    When calling SQLGetDescField, the driver does not support the SQL_DESC_TD_ACTIVITY_TYPE and SQL_DESC_TD_COST_ESTIMATE custom header description fields.

  • Kerberos and Integrated Security settings not available in macOS UI

    The settings related to Kerberos and Integrated Security cannot be configured through the driver dialog boxes on macOS. To configure these features on macOS, you must use a connection string or the odbc.ini file.

  • Catalog functions always return ODBC 3.x column names.

    For catalog functions, the driver returns the ODBC 3.x column names rather than ODBC 2.x column names, even in an ODBC 2.x environment.

  • The SQL_ATTR_ROWS_FETCHED_PTR statement attribute cannot be set properly.

    You can set a value by calling SQLSetStmtAttr(SQL_ATTR_ROWS_FETCHED_PTR), but the value is reset after you close the cursor. The value that you set does not persist.

  • In specific cases, during INSERT operations that require the data to be truncated, there is no message indicating that truncation has occurred.

    This behavior occurs when:
    • The Session Mode option (the SessionMode property) is set to Teradata.
    • The driver inserts data that is too large for the target column.

    The database truncates the data to fit, but the message indicating that truncation has occurred is not returned. The driver expects the database to report the truncation. However, when Session Mode is set to Teradata, the database does not return the truncation message.

  • When you try to bind NUMERIC data to a parameter array, a database error occurs.

    Binding NUMERIC data to parameter arrays is not supported.

Version History ==============================================================

16.20.00 ———————————————————————

Released 2017-07-07

Enhancements & New Features

  • Improved performance for SELECT and INSERT statements

    The driver can now complete SELECT and INSERT operations faster than in previous versions.

  • Unicode Pass Through

    You can now configure support for Unicode Pass Through (UPT). To specify whether the driver supports UPT, set the UPT Mode option (or the UPTMode property). For more information, see the Installation and Configuration Guide.

  • CSV support

    You can now use the driver to work with comma-separated values (CSV).

    Teradata Database supports CSV starting from version 16.20.

  • New SQL columns containing time series information

    When SQLTables is called, the results now include the TD_TABLE_FLAVOR column. This column contains indicators for the primary table indexes of tables that store time series data.

    When SQLStatistics is called, the results now include the TD_TIMEZERO and TD_TIMEBUCKET columns. TD_TIMEZERO contains the timestamp indicating the start of the time series, while TD_TIMEBUCKET contains the length of time in the time series.

  • Japanese error messages

    The driver is now able to return error messages in Japanese. To specify whether the driver returns error messages in English or Japanese, set the Locale connection property. For more information, see the Installation and Configuration Guide.

  • DATE data for TIMESTAMP parameters

    You can now configure the driver to use DATE data for SQL_C_TIMESTAMP and SQL_TIMESTAMP parameters, enabling compatibility with applications that use Microsoft Access Jet databases. To do this, enable the Use DATE Data For TIMESTAMP Parameters advanced option (the UseDateForTimestamp property). For more information, see the Installation and Configuration Guide.

  • Authentication parameter support

    You can now specify authentication parameters by setting the Parameter option (the AuthenticationParameter property). For more information, see the Installation and Configuration Guide.

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 16.20.00.

  • Driver displays dialog box prompting for password renewal even when SQL_DRIVER_NOPROMPT has been set.

  • When executing a multi-statement query asynchronously, the driver stops responding if SQLCancel is called.

  • When a connection fails due to a dependency issue, the DSN Setup dialog box terminates unexpectedly.

  • In some cases, numeric values that are used in parameters are converted incorrectly.

  • In some cases, an “out of range” error occurs when rebinding a numeric value after it has been converted to a different type.

  • When calling SQLGetTypeInfo, the driver always returns CHARACTER columns as SQL_WVARCHAR columns.

    This issue has been resolved. The driver now returns either SQL_VARCHAR or SQL_WVARCHAR depending on the encoding used in the database.

16.07.00 ———————————————————————

Released 2017-05-15

Enhancements & New Features

  • Updated Teradata Tools and Utilities to version 16.10

    The driver now uses Teradata Tools and Utilities (TTU) 16.10. Previously, the driver used TTU 16.00.

  • Additional options for specifying character set

    As alternatives to using the Session Character Set option (the CharacterSet connection property), when using the Linux or macOS driver you can now use the IANAAppCodePage or AppCodePage connection properties to specify the character set to use for your connection.

  • Custom translation DLL files

    The driver now supports user-defined translation DLL files, providing improved and more varied language support.

  • Custom IPDs and APDs

    You can now use the driver to set and get custom IPDs (Implementation Parameter Descriptors) and APDs (Application Parameter Descriptors).

  • Date Time Format drop-down list on macOS

    When using the macOS driver, you can now use a drop-down list in the DSN configuration dialog box to set the Date Time Format option. Previously, you could only set this option through a connection string setting.

  • Improved support for encoding types

    The Linux and macOS drivers now support the ibm-862_P100-1995 and ibm-868_P100-1995 encoding types, and you can set the IANAAppCodePage and AppCodePage connection properties to these values.

  • Smart LOB retrieval mode

    You can now optimize driver performance when retrieving Large Object (LOB) data by configuring Smart LOB (SLOB) Mode. For more information, see the Installation and Configuration Guide.

  • Support for DataDirect driver manager version 7.1.6.233

    The driver is now compatible with version 7.1.6.233 of the DataDirect driver manager.

  • Improved performance when retrieving information about catalog functions

    The driver has been upgraded to use more efficient SQL queries when retrieving information about catalog functions.

  • Locale settings

    You can now set the Locale property in a connection string to specify the locale to use for error messages.

  • Complete authentication support

    The driver now provides full support for the following authentication mechanisms:
    • Kerberos
    • LDAP
    • SPNEGO
    • TDNEGO
    • TD2

    Previously, only TD2 was fully supported.

  • Increased maximum size for response buffer

    When connected to databases instances that are running Teradata Database 16.00 or later, the driver supports a maximum response buffer size of 7MB. For connections that use earlier versions of Teradata Database, the maximum response buffer size remains at 1MB.

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 16.07.00.

  • SQLProcedures disregards the specified procedure name, and instead returns all procedures that have the specified schema name.

  • In some cases, when executing a multi-statement query, the driver returns the incorrect column names.

  • When executing a BEGIN QUERY CAPTURE query, an error occurs.

    Before, this error occurred because the driver tried to prepare the statement before executing it, but BEGIN QUERY CAPTURE queries cannot be prepared. This issue has been resolved, and the driver now executes these queries without preparing them.

  • The driver seems to connect successfully when using an invalid name or IP address.

    Before, the driver erroneously returned SQL_SUCCESS_WITH_INFO even though the connection failed. This issue has been resolved, and the driver now returns SQL_ERROR.

  • When retrieving PERIOD data that is NULL, the driver returns an error.

  • In some cases, the driver corrupts the BLOB data that it retrieves.

  • In some cases, the driver fails to allocate buffers for data.

    This issue occurred because the driver erroneously allocated buffers based on the column length specified in the metadata instead of the actual length of the data value. This resulted in buffers that were too large to be allocated. This issue has been resolved, and the driver now creates buffers that are the appropriate size for the data.

  • When using a connection string that has the Password property set to an unencrypted password value, the driver fails to connect.

  • When calling SQLSpecialColumns with a non-NULL identifier type, an error occurs.

  • When configuring the driver on Windows using the Simba Teradata ODBC Driver DSN Setup dialog box, the Session Character Set drop-down list is missing the LATIN1252_3A0 setting.

  • The driver reports incorrect display sizes for SQL_NUMERIC and SQL_DECIMAL data when the precision is equal to the scale.

  • SQLStatistics does not return any rows.

  • Before connecting to the database, the driver erroneously reports that it does not support transactions.

  • In some cases, SQLColumns does not return the correct catalog name or column length, and does not properly handle aborted transactions.

  • When calling catalog functions, the driver always returns CHARACTER columns as SQL_WVARCHAR columns.

    This issue has been resolved for all catalog functions except for SQLGetTypeInfo. For these catalog functions, the driver now returns either SQL_VARCHAR or SQL_WVARCHAR depending on the encoding used in the database.

  • Before connecting to the database, the driver does not allow autocommit mode to be disabled.

    This issue occurred because, before connecting, the driver would erroneously report that it did not support transactions. This issue has been resolved.

  • In some cases, SQLProcedureColumns returns the incorrect column size and Teradata (TDODBC) data type.

    This issue occurred because the driver failed to recognize whether a unicode character set was being used for the session.

  • In some cases, the driver processes the names of UDTs (user-defined types) incorrectly.

  • In some cases, queries that contain question marks (?) do not work as expected.

    This issue occurred because the driver treated all question marks (?) in queries as parameter markers.

  • In some cases, memory leaks occur when calling SQLDriverConnectW, SQLConnectW, SQLSetConnectAttr, and SQLGetConnectAttr.

  • Escape sequences for INTERVAL DAY values without precision are not parsed correctly.

    For example, previously, the driver would translate {{INTERVAL ‘1’ DAY} as CAST(‘1’ AS INTERVAL DAY) instead of (INTERVAL ‘1’ DAY). This issue has been resolved and the driver now translates these escape sequences correctly.

  • SQL_NUMERIC and SQL_DECIMAL parameters do not accept NULL values.

  • In some cases, the result set returned by SQLSpecialColumns is incorrect.

    Previously, the driver returned results based on the UNIQUEFLAG column property and did not verify whether the table can contain duplicate rows. The driver now returns an empty result set if it detects that the table can contain duplicate rows, since there is no set of columns in that table that can uniquely identify a row.

  • When calling SQLProcedureColumns, the driver does not report MACROs because it does not recognize MACRO identifiers.

  • The driver fails to display unicode table names and indexes.

  • Driver cannot bind Interval literals to SQL_C_CHAR.

  • Some custom Teradata attributes are not supported.

    Previously, the following custom Teradata attributes are not supported:
    • SQL_COLUMN_FORMAT
    • SQL_COLUMN_CHARACTER_SET
    • SQL_COLUMN_ACTUAL_NAME
    • SQL_COLUMN_TDODBC_TYPE
    • SQL_COLUMN_EXPORT_WIDTH
    • SQL_COLUMN_EXPORT_BYTES
    • SQL_COLUMN_EXPORT_WIDTH_ADJ

    This issue has been resolved, and you can now use the driver to work with these custom attributes.

  • When you call SQLTables but filter the data based on TableType only, the driver returns an incorret rowcount (-1) but returns the correct data.

    The driver returns the correct rowcount in addition to the correct data.

  • In some cases, SQLProcedureColumns returns rows in an incorrect order.

    This issue has been resolved, and the driver now returns the parameters in the order that is specified in the procedure definition in the ODBC specification.

16.06.02 ———————————————————————

Released 2017-03-24

Enhancements & New Features

  • New driver options

    The following options have been implemented in the driver:
    • Use Column Names (the DontUseTitles property)
    • Use Regional Settings For Decimal Symbol (the UseRegionalSettings property)
    • Log Error Events (the LogErrorEvents property)

    The Log Error Events option is available only in the Windows driver. It is a driver-wide option that affects all connections that use this driver, and it cannot be set as a connection string property.

    For more information about these new options, see the Installation and Configuration Guide.

  • New advanced options

    The following advanced options have been implemented in the driver:
    • Procedure With Print Stmt (the ProcedureWithPrintStmt property)
    • Procedure With SPL Source (the ProcedureWithSplSource property)
    • DataSource DNS Entries (the DataSourceDNSEntries property)
    • Retry System Calls (EINTR) (the RetrySystemCalls property)
    • Enable Custom Catalog Mode For 2.x Applications (the EnableCustomCatalogMode property)
    • Return Empty String In CREATE_PARAMS Column For SQL_TIMESTAMP (the ReturnEmptyString property)
    • Return Max. CHAR/VARCHAR Length As 32K (the ReturnMaxLengthAs32k property)

    For more information about these new options, see the Installation and Configuration Guide.

  • Support for Avro datasets

    You can now use the driver to work with data that is stored in Avro format.

    The Avro format is available in Teradata Database starting from version 16.00. For more information about this data type, see the “Teradata DATASET Data Type” document for the 16.00 release: http://www.info.teradata.com/download.cfm?ItemID=1007206

  • Parcel content validation

    The driver now validates the contents of the parcels received from the server. If an invalid field is found, then the driver cancels the operation and returns an error.

  • Improved error messaging

    If a timeout occurs when executing a HELP SESSION or HELP DATABASE query, the driver now returns the following error message: “Query delayed too long or no response from the database when setting default database to ”.

    Before, the driver returned the following message for this type of error: “No response received when attempting to connect to the Teradata server”. This message caused the error to sometimes be mistaken for a socket error.

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 16.06.02.

  • Under specific circumstances, when converting data from a numeric type to SQL_C_CHAR, the driver returns an incorrect value for SQL_DESC_DISPLAY_SIZE.

    Before, if the numeric data that is being converted has both of the following features, the driver returns a SQL_DESC_DISPLAY_SIZE that is one less than the correct value:
    1. The scale and the precision are the same.
    2. The number is negative.

    The driver now returns the correct value for SQL_DESC_DISPLAY_SIZE.

  • When calling SQLProcedureColumns, the driver returns the stored procedure parameters in the wrong order.

  • When calling SQLProcedureColumns, the driver returns an incorrect DATA_TYPE value for ASCII data.

    The driver now returns a DATA_TYPE value based on the setting specified for the Session Character Set option (the CharacterSet property). For more information about this option, see the Installation and Configuration Guide.

  • When SQL_ATTR_AUTOCOMMIT is set to SQL_AUTOCOMMIT_OFF before the connection is established, SQLDriverConnect returns SQL_SUCCESS_WITH_INFO.

    SQLDriverConnect now returns SQL_SUCCESS as expected.

  • When SQL_ATTR_AUTOCOMMIT is set to SQL_AUTOCOMMIT_OFF, SQLDisconnect returns an error and fails to disconnect.

  • Driver fails to connect to Microsoft Access 2016, and returns the following error message: “Reserved error (-7747); there is no message for this error.”

  • The default value of SQL_MAX_CATALOG_NAME_LEN is hard-coded to 1024.

    The driver now sets the default value of SQL_MAX_CATALOG_NAME_LEN to the maximum column length that is supported by the database. This value varies depending on which Teradata Database version the driver is connected to. For version 14.00 and earlier, the default value is 30. For versions after 14.00, the default value is 128.

    The driver now determines the default value of SQL_MAX_CATALOG_NAME_LEN based on the detected database version, and uses the maximum column length that is supported by the particular database version.

  • When calling catalog functions, the driver returns an incorrect column size for INTERVAL, XML, and JSON type columns.

  • When inserting multiple BLOB or CLOB values, the driver returns an error.

    Before, this issue occurred because the insertion of multiple BLOB or CLOB values caused the driver to send an invalid request message to the database. The driver can now handle these insertions correctly.

  • Driver fails to return error messages for socket errors.

  • If the query contains parameters and either quotation marks or comments, the driver returns a parameter number mismatch.

    Before, the parameter marker checker incorrectly returned “No parameter” for queries that contained single quotation marks (’), double quotation marks ("), or comments. As a result, the driver did not process the parameters and sent them to the database.

    The driver now processes and sends all parameters to the database.

  • Driver returns an error when the procedure body exceeds the maximum size allowed.

    The driver can now handle a long procedure body by splitting it and sending it in multiple chunks.

  • When a connection fails because required settings are missing from the DSN, the driver does not display a prompt as expected.

    On Windows, if a saved DSN is missing settings that are required for the connection, the driver now opens a dialog box that prompts you to provide the missing settings.

  • Driver fails to process parameters that use SQL_DEFAULT_PARAM.

    The driver can now process parameters that use SQL_DEFAULT_PARAM.

    Note the following:
    • SQL_DEFAULT_PARAM is only valid in the context of a stored procedure call. If you use it outside of a stored procedure call, the driver returns an error.
    • Teradata Database does not support default parameters for stored procedures, so the driver uses NULL as the value for SQL_DEFAULT_PARAM.

  • When attempting to execute a parameterized INSERT statement with a CLOB column, a memory allocation error occurs.

    Before, this issue occurred because the driver used the maximum LOB size instead of the actual size of the bound parameter as the buffer size. The driver now uses the appropriate size when creating the buffer.

  • SQLGetInfo() call fails if it contains the SQL_KEYWORDS attribute.

    The driver now returns the correct results when the SQL_KEYWORDS attribute is used in a SQLGetInfo() call.

  • When the driver is configured to work in ANSI mode, it returns the values for Date and Time functions incorrectly.

    Before, when the Date Time Format option was set to AAA (DateTimeFormat=AAA), the driver returned Integer values instead of ANSI values for Date and Time functions, generating invalid character values for the data. The driver now returns ANSI values as expected.

  • Dynamic explain queries do not return any data.

    The driver now returns the expected data when a dynamic explain query is used.

  • When executing a query that binds SQL_DECIMAL or SQL_NUMERIC data anywhere before the last parameter in the statement, invalid parcels are generated.

    The driver is now able to execute queries that bind SQL_DECIMAL and SQL_NUMERIC parameters at any parameter index.

  • SQLDriverConnect returns generic “Failed to logon” error message when an invalid character set is provided.

    The driver now returns a more precise error message stating that the connection failed because the provided session character set is invalid.

  • SQLBrowseConnect and SQLDriverConnect return SQL_ERROR instead of SQL_NEED_DATA when the required connection settings are not provided.

    The driver now returns SQL_NEED_DATA instead, indicating that the required settings must be provided before a connection can be made.

  • When the driver returns results for a batch of semicolon-separated queries, the result sets of all the preceding queries use the same column names as the result set of the last query.

    For example, consider the following batch of queries:

    SELECT * FROM TABLE_1; SELECT * FROM TABLE_2; SELECT * FROM TABLE_3

    Before, the driver returned the result sets of SELECT * FROM TABLE_1 and SELECT * FROM TABLE_2 using the column names from the result set of SELECT * FROM TABLE_3.

    The driver now returns result sets using the correct column names.

16.01.00 ———————————————————————

Released 2016-11-25

Enhancements & New Features

  • Updated Teradata Tools and Utilities to version 16.0

    The driver now uses Teradata Tools and Utilities (TTU) 16.0. Previously, the driver used TTU 15.10.

  • LOB parameters now supported

    You can now use LOB parameters with and without DATA_AT_EXEC.

  • New parser implementation

    The Legacy Parser has been removed from the driver, and the Lightweight Parser has been reimplemented. The new parser supports more ODBC escape sequences and improves driver handling for ODBC escape sequences overall.

  • Stored procedures now supported

    You can now run stored procedures when using the driver.

  • EXPLAIN queries now supported

    You can now run EXPLAIN queries when using the driver. For example: EXPLAIN USING (p INT) INSERT INTO odbc.SENTDO191 VALUES( : p )

  • Custom Teradata data types now supported in parameters

    You can now use the following Teradata data types in parameters:
    • FIXED_NUMBER
    • FLOATING_NUMBER
    • PERIOD_DATE
    • PERIOD_TIME
    • PERIOD_TIME_TZ
    • PERIOD_TIMESTAMP
    • PERIOD_TIMESTAMP_TZ

  • Argument validation added for SQLBindParameter

    The driver now validates the colSize and decimalDigit arguments when calling SQLBindParameter.

  • Arrays of parameter values now supported

    You can now use multiple parameters values in a statement.

  • SQLBrowseConnect now supported

    You can now call SQLBrowseConnect when using the driver.

  • Password expiry prompt implemented for Windows

    If your Teradata Database password expires during a connection, the Windows version of the driver now opens a dialog box that prompts you to change your password.

  • Updated support for SQLCancel

    Before, SQLCancel was supported only for SQLExecute and SQLExecDirect. You can now use SQLCancel to cancel any operation.

  • Custom statement attributes now supported

    The driver now supports the following custom statement attributes:
    • SQL_ATTR_TDATA_HOST_ID (13001)
    • SQL_ATTR_TDATA_SESSION_NUMBER (13002)
    • SQL_ATTR_TDATA_SESSION_CHARSET (13003)
    • SQL_ATTR_AGKR (13004)
    • SQL_ATTR_DATA_ENCRYPTION (13008)
    • SQL_ATTR_TDATA_ROWCOUNT (13009)
    • SQL_ATTR_TRUSTED_SQL (13010)

  • Custom connection attributes now supported

    The driver now supports the following custom connection attributes:
    • SQL_CONNECT_TCPVENDOR (1000)
    • SQL_CONNECT_RUNSTRING (1300)

  • Updated default format for DATE values

    Before, when communicating with the database, the driver used DATE values in Integer format by default. The driver now uses DATE values in ANSI format instead. You can configure the Date Time Format option (the DateTimeFormat property) to modify this behavior.

  • Support added for querying column information from views

    When connected to an instance running Teradata Database 16.0 or later, as an alternative to using HELP commands, you can now call SQLColumns to retrieve column information from views.

Resolved Issues The following issues were resolved in Simba Teradata ODBC Driver 16.01.00.

  • When converting numeric data from SQL to C type, the driver does not use the precision and scale values from the Application Row Descriptor (ARD).

    The driver now uses the precision and scale values from the ARD, but only if values are specified in the SQL_DESC_PRECISION and SQL_DESC_SCALE fields in the ARD. Otherwise, the driver uses 38 for precision (the default value set in the driver) and 0 for scale (the default value of SQL_DESC_SCALE).

    For more information, see “HOWTO: Retrieving Numeric Data with SQL_NUMERIC_STRUCT” on the Microsoft Support website: https://support.microsoft.com/en-us/kb/222831

  • When calling SQLPrimaryKeys, the driver returns primary index values in addition to primary key values.

  • When the Enable Extended Statement Info configuration option is disabled (the EnableExtendedStmtInfo property is set to 0), the driver terminates unexpectedly.

  • Driver fails to run queries that contain wide characters.

  • When calling SQLGetInfo, the driver returns an empty value for SQL_DATABASE_NAME.

  • After executing MERGE queries, the driver returns SQL_ROWCOUNT_UNKNOWN instead of the appropriate row count value.

  • When calling SQLGetInfo, the driver returns an incomplete list for SQL_KEYWORDS.

  • In some cases, during COP discovery, a multithreading issue occurs and the driver terminates unexpectedly.

  • When calling catalog functions, the driver does not accept object names that contain more than 30 characters.

  • Driver fails to return warning messages for User Defined Types (UDTs) and User Defined Functions (UDFs).

  • When binding input parameters to SQL_TD_XML or SQL_TD_JSON, an error occurs.

16.0.0 ———————————————————————–

Released 2016-05-31

  • Version 16.0.0 is the initial release of the Simba Teradata ODBC Driver.

==============================================================================