Connect with the NEWLOCALE and NEWCODESET properties

Because new locales may be created between updates of these tables, two connection properties, NEWLOCALE and NEWCODESET, let you specify a locale or code set that is not specified in the tables. Here is an example URL using these properties:

jdbc:onedb://myhost:1533;
   user=myname; password=mypasswd;NEWLOCALE=en_us,en_us;
   NEWCODESET=8859_1,8859-1,819;

A URL must be on one line.

The NEWLOCALE and NEWCODESET properties have the following formats:

NEWLOCALE=JDK-locale,Ifx-locale:JDK-locale,Ifx-locale...

NEWCODESET=JDK-encoding,Ifx-codeset,Ifx-codeset-number:JDK-
   encoding, Ifx-codeset,Ifx-codeset-number...

There is no limit to the number of locale or code-set mappings you can specify.

You can connect to an NLS database by defining a locale using NEWCODESET and NEWLOCALE connection properties.

If you specify an incorrect number of parameters or values, you get a Locale Not Supported or Encoding or Code Set Not Supported message.

If these properties are set in the URL or a DataSource object, the new values in NEWLOCALE and NEWCODESET override the values in the JDBC internal tables. For example, if JDBC already maps 8859-1 to 8859_1 internally, but you specify NEWCODESET=8888,8859-1,819 instead, the new value 8888 is used for the code-set conversion.