No new features have been added to the Teradata Provider 13.01.00.03 Release.
No new features have been added to the Teradata Provider 13.01.00.01 Release.
Interval types have been added. These are Provider Specific Types that are equivalent to the Teradata Database's Interval types. The new types are as follows:
TdIntervalDay Equivalent to the Teradata Database Interval Day (precision) data type.
TdIntervalDayToHour : Equivalent to the Teradata Database Interval Day (precision) To Hour data type.
TdIntervalDayToMinute : Equivalent to the Teradata Database Interval Day (precision) To Minute data type.
TdIntervalDayToSecond : Equivalent to the Teradata Database Interval Day (precision) To Second (fractional precision) data type.
TdIntervalHour : Equivalent to the Teradata Database Interval Hour (precision) data type.
TdIntervalHourToMinute : Equivalent to the Teradata Database Interval Hour (precision) To Minute data type.
TdIntervalHourToSecond : Equivalent to the Teradata Database Interval Hour (precision) To Second (fractional precision) data type.
TdIntervalMinute : Equivalent to the Teradata Database Interval Minute (precision) data type.
TdIntervalMinuteToSecond : Equivalent to the Teradata Database Interval Minute (precision) To Second (fractional precision) data type.
TdIntervalSecond : Equivalent to the Teradata Database Interval Second (precision, fractional precision) data type.
TdIntervalYearToMonth : Equivalent to the Teradata Database Interval Year (precision) To Month data type.
TdIntervalMonth : Equivalent to the Teradata Database Interval Month (precision)) data type.
TdIntervalYear : Equivalent to the Teradata Database Interval Year (precision) data type.
Support for the Teradata Graphic Server Character Set has been added.
Query Band and Trusted Session support has been added at the connection and transaction levels. The TdQueryBand object will manage the Query Band definitions.
Support for IPV6 has been added.
Support for DateTimeOffset has been added. Applications can send data of type DateTimeOffset to Teradata, and receive data from Teradata as a DateTimeOffset type. This feature can be turned off by setting the Connection String Attribute EnableDateTimeOffset to false.
The installation package for the .NET Data Provider for Teradata is now digitally signed. The digital signature assures that the installation package has not been tampered with or altered by a third party.
The TdError type contains a new property called Info. For syntax errors the Info property will contain the character position of the parser syntax error in the command text. For other errors the content meaning will vary.
The Teradata Database would return the error "Locator is invalid because it has been changed" when filling a DataTable that contains a LOB data. This occurs when TdDataAdapter.FillSchema is called to populate the DataTable with schema information, and then calling TdDataAdapter.Fill. This will no longer occur.
The Parse methods of TdTimestampWithTimeZone and TdTimeWithTimeZone was unable to parse a string that did not contain a UTC offset. A FormatException gets thrown. The Parse methods have been fixed so that a string that does not contain a UTC offset can be succesfully parsed.
There are some applications that add a new line character to the CommandText. When the command is executed, the Teradata Database will throw an error indicating that the new line character is not a valid token. The provider will now remove the new line character before submitting the command to Teradata.
The documentation for the Add and Subtract methods for TdPeriodTime and TdPeriodTimeWithTimeZone incorrectly stated that an ArithmeticException will get thrown when the operation results with the beginning bound of the period being greater than or equal to the ending bound. This has been changed to state that a TdException will get thrown.
"00:00" was used as the default offset when TdTimestampWithTimeZone and TdTimeWithTimeZone objects are created using constructors that do not include a UTC offset parameter. This default was also being used when a "timestamp" or "time" was implicitly converted to a TdTimestampWithTimeZone or TdTimeWithTimeZone, respectively. This has changed so that the local offset of the machine is used as the default offset.
This change in behavior also affects TdPeriodTimestampWithTimeZone and TdPeriodTimeWithTimeZone.
The end bound of a period was not being correctly handled when explicitly converted to another Period type. Suppose a period has an end bound that is equivalent to the UNTIL_CHANGED value. When it is converted to another Period type, the end bound of the resulting period was not being set to the equivalent UNTIL_CHANGED value of the targeted period.
This has been fixed so that the UNTIL_CHANGED value of the source is converted to the equivalent UNTIL_CHANGED value of the targeted period type during an explicit conversion operation. This affects conversions to TdPeriodTimeWithTimeZone and TdPeriodTimestampWithTimeZone.