Send feedback on this topic.
Teradata.Client.Provider
Teradata Implementation Specifics
.NET Data Provider for Teradata > Developer's Guide > ADO.NET Entity Provider for Teradata > Teradata Implementation Specifics
.NET CORE   This feature is not supported by the .NET Core implementation of the Data Provider.

As discussed in the Overview the Entity Framework invokes the Entity Provider for Teradata to interpret the LINQ to Entities and Entity SQL statements contained in an application to Teradata SQL statements. In order to use Entity Provider for Teradata, the following must be done:

LINQ to Entities or Entity Sql are used to query an EDM. When these type of statements are executed within an application the following tasks are performed by the Entity Framework:

  1. The Entity Framework processes the statement and generates an object called a Command Tree
  2. The Entity Framework invokes the Entity Provider for Teradata and passes the Command Tree object.
  3. The Entity Provider processes the Command Tree and generates the SQL statement that will be executed by the Teradata Database.
  4. The data is returned to the application via the Framework.

When the Entity Provider is generating the SQL statement based on the information passed by the Framework, there are scenarios that require the Entity Provider for Teradata to build SQL clauses that require special processing. This special processing usually involves the casting of column.

This section discusses items in the Entity Framework that are specific to Teradata.

In This Section

Using the Entity Provider with Different Teradata Versions

Data Type Mappings

Canonical Functions

Teradata Namespace Functions

Processing Set Operations and Case Statements

Updating Entities with Time With Time Zone, Period and Year/Month Intervals Properties

Working with Parameters