Support for HCL OneDB GLS variables
Globalization adds several environment variables to HCL OneDB™ JDBC
Driver,
which are summarized in the following table.
Supported HCL OneDB environment variables | Description |
---|---|
CLIENT_LOCALE | Specifies the locale of the client that is accessing the database. Provides defaults for user-defined formats such as the GL_DATE format. User-defined data types can use it for code-set conversion. Together with the DB_LOCALE variable, the database server uses this variable to establish the server processing locale. The DB_LOCALE and CLIENT_LOCALE values must be the same, or their code sets must be convertible. |
DBCENTURY | Enables you to specify the appropriate expansion for one- or two-digit year DATE values |
DBDATE | Specifies the end-user formats of values in DATE columns. Supported for compatibility with earlier versions; GL_DATE is preferred. |
DB_LOCALE | Specifies the locale of the database. HCL OneDB JDBC Driver uses this variable to perform code-set conversion between Unicode and the database locale. Together with the CLIENT_LOCALE variable, the database server uses this variable to establish the server processing locale. The DB_LOCALE and CLIENT_LOCALE values must be the same, or their code sets must be convertible. |
GL_DATE | Specifies the end-user formats of values in DATE columns |
GL_USEGLU | To enable Unicode collation by Java/JDBC client applications with the International Components for Unicode (ICU), specify GL_USEGLU=1 in the connection string before connecting to the HCL OneDB instance. This enables the server to use advanced Unicode converters that are required to work with Java™. The GL_USEGLU environment variable must be set to a value of 1 (one) in the database server environment before the server is started, and before the database is created. |
NEWCODESET | Allows new code sets to be defined between releases of HCL OneDB JDBC Driver. |
NEWLOCALE | Allows new locales to be defined between releases of HCL OneDB JDBC Driver. |
The HCL OneDB JDBC Driver does not change the decimal format, even if there is a CLIENT_LOCALE setting available. Globalization should be done within the Java application with the DecimalFormat class.
Important: The DB_LOCALE, CLIENT_LOCALE,
and GL_DATE variables are supported only if the
database server supports the feature.