![]() |
Localizing Cloudscape
|
Reference Manual |
Database LocaleCloudscape databases vary their behavior according to locales in the following ways:
Setting a Database's LocaleYou set the locale for a database when you create it, or in the case of databases created prior to Version 3.5, when you upgrade it. After the database is created or upgraded to a post-3.0 version, you cannot change a database's locale. If you do not explicitly specify a locale, Cloudscape uses the locale of your machine, which is automatically detected by your JVM (the value returned by java.lang.Locale.getDefault.) To override the default locale, explicitly set the locale using the locale attribute on the database connection URL when you create or upgrade the database. You specify the locale with a two-lowercase-letter code for the language, followed by an underscore (_), followed by a two-uppercase-letter code for the country. Examples and more details are provided in locale=ll_CC in the Cloudscape Reference Manual. Some example database connection URLs: jdbc:cloudscape:germanDB;create=true;locale=de_DE jdbc:cloudscape:japaneseDB;upgrade=true;locale=ja_JP NOTE: In synchronized systems, you cannot set the locale of a target to be different than the locale of the source. When upgrading Version 3.5 source databases, targets inherit the new locale on the first refresh. Finding Out a Database's LocaleCOM.cloudscape.database.Database has a method called getLocale that returns the locale of the database. Within an SQL-J statement: |
|
![]() Cloudscape Version 3.6 For information about Cloudscape technical support, go to: www.cloudscape.com/support/.Copyright © 1998, 1999, 2000 Informix Software, Inc. All rights reserved. |