Send feedback on this topic.
Teradata.Client.Provider
Limitations Using the Current Session Character Set and the Entity Provider
.NET Data Provider for Teradata > Developer's Guide > ADO.NET Entity Provider for Teradata > Restrictions using the Entity Framework with Teradata > Restrictions using the Entity Provider > Limitations Using the Current Session Character Set and the Entity Provider
.NET CORE   This feature is not supported by the .NET Core implementation of the Data Provider.

Limitations Using the Current Session Character Set and the Entity Provider

It is recommended to use a Unicode session character set in order to fully support all object names in the Entity Provider. If a character cannot be represented within the current client session character set, the Advanced SQL Engine will return a translation error character in the object name. The object name in this form cannot be submitted back to Teradata using the Entity Provider. For this reason the session character set that is used to generate the Entity Data Model (EDM) must also be used in generating EDM queries.

For more information on extended object name support in the .NET Data Provider see Extended Object Names in the Data Provider.