Connection Type | How the system determines the Session Character Set |
---|---|
CLIv2 | You can specify the client character set in several ways. The system determines the client character set for a session according to the following order of precedence. Each higher numbered item, if it exists, supersedes the previous item. For Mainframe connections (TDP) the following determines the default character set:
For Gateway connections the following determines the default character set:
|
Teradata JDBC Driver | The Teradata JDBC Driver determines the session character set solely by the CHARSET connection parameter. If the CHARSET connection parameter is omitted, the Teradata JDBC Driver uses the ASCII session character set. See Assigning the Default Client Character Set for a Session. |
ODBC Driver for Teradata | An application or a user can specify the session character set option in the connection string for the connection. See Assigning the Default Client Character Set During Client Setup. |
.NET Data Provider for Teradata | An application or a user can specify the session character set option in the connection string for the connection. The .NET Data Provider defaults the session character set to ASCII when an application or user does not specify a session character set connection string option. See Assigning the Default Client Character Set During Client Setup. |