Specifies the language, territory, and code set that the client application uses in I/O operations, end user formats, and processing ESQL statements.
Syntax
CLIENT_LOCALE=<language>_<territory>.<code_set>@modifier
Possible values
<language> |
Two-character name that represents the language for a specific locale. |
<territory> |
Two-character name that represents the cultural conventions. For example, territory might specify the Swiss version of the French, German, or Italian language. |
<code_set> |
Name of the code set that the locale supports. |
@modifier |
Optional locale modifier that has a maximum of four alphanumeric characters. The modifier specification modifies the cultural-convention settings that the language and territory settings imply. The modifier can indicate a localized collating order that the locale supports. For example, you can set @modifier to specify dictionary or telephone-book collation order. |
Usage
CLIENT_LOCALE specifies the language, territory, and code set that the client application uses in I/O operations, end user formats, and processing ESQL statements.
When a client application and a database server exchange character data, the client application performs code-set conversion when the code set of the CLIENT_LOCALE environment variable is different from the code set of DB_LOCALE (on the client computer).
Code-set conversion prevents data corruption when these two code sets are different.
If CLIENT_LOCALE is not defined the value of the default system locale is sent to the database.
To get the list of available locales on UNIX platform, run the locale -a command. On Windows platforms, search the Microsoft MSDN documentation for "Language and Country/Region Strings".
CLIENT_LOCALE applies at runtime (inet.env).
Example
Setting the French locale for Canada, and the ISO 8859-1 character set will look as follows:
CLIENT_LOCALE=fr_ca.8859-1