Resolved issues track corrections and updates to Teradata Tools and Utilities software and to documentation affected by the updates.
| Issue | Description |
|---|---|
| ODBC-17940 | Fixed issue of SQLTables function returns incorrect values in TD_TABLE_FLAVOR column. |
| ODBC-17941 | Fixed issue of SQLTables returning only a subset of tables when parameters are empty strings. |
| ODBC-18089 | Fixed: When session character set is set to UTF8, store procedures do not set the values of the output (OUT and INOUT) parameters. |
| TDS-77, TDS-78 | Kerberos and Integrated Security settings not available in the macOS UI. On macOS, you can now configure the settings related to Kerberos and Integrated Security using the driver dialog boxes, in addition to configuring them through a connection string or the odbc.ini file. |
| TDS-80 |
In the macOS UI, the "UPT Mode" option is mislabeled with an incorrect requirement. Before, in the Driver Options dialog box on macOS, the requirement "V2R16 and above" is shown under the "UPT Mode" option. This requirement does not actually apply to the UPT Mode option, so that text has been removed from the dialog box. * When converting a SQL_C_NUMERIC value to SQL_FLOAT or SQL_DOUBLE, if the source value contains more significant digits than the target type allows, the driver silently truncates excess digits and returns SQL_SUCCESS. The driver now returns an error with SQL state 22003 and does not truncate the value. |
| TDS-82 | returns a "memory allocation error" when bound parameters are close to the 1MB size limit, but do not actually exceed this limit. This error occurred because the driver adds packet overhead to the outgoing message, which can cause the message to exceed the 1MB limit. The driver now returns a more accurate error message when this scenario occurs: "SQL request with parameters exceeds maximum allowed length of 1MB". |
| TDS-85 | When you call SQLTables using a wildcard character for the schema name and without specifying a table name, the driver returns a record for each table in the database. The driver now returns a record for each schema, as expected. |
| TDS-95 | In some cases, when using the driver in a .NET application, the connection fails because the connection string exceeds 1023 characters. The OutConnectionString returned by SQLDriverConnect has been optimized to avoid exceeding the length limit. |
| TDS-109 | When executing a batch INSERT operation on a NUMBER column, the driver inserts incorrect data values. Before, the driver erroneously inserted the first value in the batch multiple times. The driver now inserts all the specified values as expected. |
| TDS-110 | When executing a batch INSERT operation on a NUMBER column, the driver inserts incorrect data values. Before, the driver erroneously inserted the first value in the batch multiple times. The driver now inserts all the specified values as expected. |
| TDS-113 | User credentials can be exposed in the driver's tracing log if they are passed in through a connection string. Values such as user name and password are no longer included in the tracing logs. |
| TDS-117 | Setting the Database property in the connection string does not override the DefaultDatabase setting saved in the DSN. You can now set the Database property in a connection string to override the DefaultDatabase setting saved in the DSN that you are using to connect to Teradata Database. This is the expected behavior, because settings specified in connection strings should take precedence over settings saved in DSNs, and the Database key is synonymous with the DefaultDatabase key. |
| TDS-132 | When you rename a DSN, the driver creates an additional DSN with the new name instead of just updating the name of the existing DSN. |
| TDS-133 | Previously, when the Connection dialog box reopens after insufficient connection information had been provided, the dialog box did not contain all of the information that has already been specified through the DSN or connection string. The driver now consistently populates the Connection dialog box with any information that has already been provided. |
| TDS-139 | When establishing a connection based on a DSN-less connection string, the driver does not use the correct default session mode. |