LOBs are now optimized when sent to the Teradata Database. In previous releases of the .NET Data Provider for Teradata LOBs were sent to a Teradata Database using deferred mode. This would be done whether the size of the LOB was 1 byte or 2 gigabytes. The handling of LOBs has been modified such that LOBs that can fit within the size restrictions of the data being sent to Teradata will either be included as a Smart-LOB (SLOB) or In-Lined in the parameter data. LOBs that exceed the size restrictions will continue to be sent using deferred mode.
A LOB will be sent as a SLOB when connected to a Teradata Database 15.0 or later. In-Lining will be used when connected to Teradata Database 14.0 and 14.10. LOBs will be sent as deferred when the provider is connected to a Teradata Database earlier than 14.0.
A new restriction (PK_TABLE_SCHEMA) has been added to ForeignKeys schema collection.
The Data Provider supports JSON data type. TdDataReader.GetString, TdDataReader.GetChars and TdDataReader.GetTdClob methods support JSON data retrieval. Similarly an application can set TdParameter.Value to a String, Char[] or TextReader in order to send JSON data to the Teradata Database.
The Entity Provider supports Entity Framework 4.0 Canonical functions with the exception of spatial functions which will be supported in a future release.
TdCommandBuilder.DeriveParameters method set the TdParameter.Size property to the "maximum number of bytes" for a parameter declared as "Character Set Unicode". The Data Provider has been enhanced to set the TdParameter.Size property to "maximum number of characters".
It was possible for the provider to get into a "hanged" state under the following scenario:
When a statement in the batch generates an error, the Teradata Database will return a Statement error parcel back the Data Provider. The StatementError parcel was not correctly being handled which was causing the Data Provider to go into a "hanged" state. This problem has been fixed.
The Entity Model Designer did not add a stored procedure or a function to the Entity Data Model when the stored procedure or function had one or more Number parameters. This problem has been fixed.
SchemaLoader returned an "Cannot set COLUMN_INFO" error while loading metadata about views when one or more view column is a number datatype. This problem has been fixed.
The Entity Model Designer did not add a table or a stored procedure or a function to the Entity Data Model when the table or stored procedure or function had one or more Xml columns or Xml parameters. This problem has been fixed.