The results of comparisons on strings, and the sort order of strings, in part depends on the character set, collation, and encoding properties of the database.
Choosing the correct character set, collation, and encoding properties for your database is primarily determined by:
The sort order you require. You should choose the collation that best sorts the characters you intend to store in your database.
The platform of your device. Requirements among supported devices can vary, and some require that you use UTF-8 to encode your characters. If you need to support multiple devices, you need to determine whether a database can be shared.
If you are synchronizing data, which languages and character sets are supported by the consolidated database. You must ensure that the character sets used in the UltraLite database and the consolidated database are compatible. Otherwise, data could be lost or become altered in unexpected ways if characters in one database's character set do not exist in the other's character set. If you have deployed UltraLite in a multilingual environment, you should also use UTF-8 to encode your UltraLite database.
When you synchronize, the MobiLink server converts characters as follows:
The UltraLite database characters are converted to Unicode.
The Unicode characters are converted into the consolidated database's character set.
Character sets and collations for UltraLite Java edition See alsoUltraLite platform requirements for character set encoding
UltraLite supported collations
 |
Discuss this page in DocCommentXchange.
|
Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1 |