UltraLite Database User's Guide
UltraLite Databases
Character sets in UltraLite
If you create an UltraLite database schema using the schema painter, you specify the character set and collating sequence as you create the database schema.
UltraLite applications use the native multi-byte character encoding of the target platform for reasons of efficiency. When the reference database uses a different character encoding, the UltraLite application uses the default collation of the target device.
UltraLite applications use the collating sequence of the reference database if either of the following conditions is met.
The reference database uses a single-byte character set.
The native character encoding of the target device is multi-byte, the reference database uses the same multi-byte character encoding, and the UltraLite analyzer can find a compact representation for the collation sequence used by the reference database.
For example, if you use a 932JPN reference database to build an UltraLite application for the Windows CE platform, the application will use Unicode and the default Unicode collation information. If, instead, you use a 932JPN reference database to build an application for the Japanese Palm Computing Platform, then the UltraLite application can inherit the collation information because the native character encoding is the same as that of the reference database.
If the character set is single byte, or the native character set of the target device is the same as the character set of the reference database, columns that are CHAR(n) or VARCHAR(n) compare and sort according to the collation sequence of the reference database.
For information about creating databases, see The UltraLite Schema Painter.
The way that character data is stored depends not only on the collation sequence used when creating the schema, but also on the character set (ANSI or Unicode) of the UltraLite runtime library that manages the database.
For more information, see UltraLite runtime character sets.