New download synchronization statistics are available   UltraLite now supports three new synchronization statistics for downloads in the syssyncresult system table—ignored_updates, ignored_deletes, and truncate_deletes.

The ignored_updates parameter indicates the number of duplicate rows that are received in the download. The ignored_deletes parameter indicates the number of deleted rows received in the download of rows that have already been deleted. The truncate_deletes parameter indicates the number of rows that were deleted in the download by a truncate operation, which is accomplished by returning NULL column values in the download_delete_cursor script.

See:

• syssyncresult system table
• ul_sync_stats_download structure [UltraLite C and Embedded SQL datatypes]
• ul_sync_stats_upload structure [UltraLite C and Embedded SQL datatypes]
• download_delete_cursor scripts
• ULSyncProgressData class [UltraLite.NET]

ZLIB compression supported on BlackBerry smartphones   The UltraLiteJ API now supports ZLIB data compression for BlackBerry smartphones when synchronizing with a MobiLink server.

See:

• MobiLink client network protocol options
• StreamHTTPParms.setZlibCompression method [UltraLiteJ]
• StreamHTTPParms.setZlibDownloadWindowSize method [UltraLiteJ]
• StreamHTTPParms.setZlibUploadWindowSize method [UltraLiteJ]
• StreamHTTPParms.zlibCompressionEnabled method [UltraLiteJ]

End-to-end (E2EE) encryption supported on BlackBerry smartphones   The UltraLiteJ API now supports end-to-end encryption for BlackBerry smartphones when synchronizing with a MobiLink server.

See:

• MobiLink client network protocol options
• StreamHTTPParms.getE2eePublicKey method [BlackBerry] [UltraLiteJ]
• StreamHTTPParms.setE2eePublicKey method [BlackBerry] [UltraLiteJ]
• StreamHTTPParms.E2EE_RSA variable [BlackBerry] [UltraLiteJ]
• StreamHTTPParms.getE2eeType method [BlackBerry] [UltraLiteJ]
• StreamHTTPParms.setE2eeType method [BlackBerry] [UltraLiteJ]

HTTP authentication supported on BlackBerry smartphones   The UltraLiteJ API now supports HTTP authentication for BlackBerry smartphones.

Passwords are revealed inside HTTP headers, but the HTTPS protocol can be used to encrypt the headers and protect the password.

See:

• StreamHTTPParms.setHTTPUserIdAndPassword method [BlackBerry] [UltraLiteJ]
• StreamHTTPParms.getHTTPUserId method [BlackBerry] [UltraLiteJ]
• StreamHTTPParms.getHTTPPassword method [BlackBerry] [UltraLiteJ]

Custom HTTP headers supported on BlackBerry smartphones   The UltraLiteJ API now supports custom HTTP headers for BlackBerry smartphones.

See:

• StreamHTTPParms.addCustomHTTPHeader method [BlackBerry] [UltraLiteJ]
• StreamHTTPParms.getCustomHTTPHeaders method [BlackBerry] [UltraLiteJ]

Index hashing supported on BlackBerry smartphones   Use the WITH MAX HASH SIZE clause to adjust index hash sizes in an UltraLite Java edition database.

See:

• Optimal hash size limit
• Connection.OPTION_MAX_HASH_SIZE variable [UltraLiteJ]
• CREATE TABLE statement [UltraLite]
• ALTER TABLE statement
• CREATE INDEX statement [UltraLite]
• ALTER INDEX statement
• sysindex system table

Indexing performance improvements for BlackBerry smartphones   Performance improvements have been made to indexing to reduce the number of pages written when committing inserts, updates, and deletes.

Fewer page reads and writes are needed when single inserts are performed. CPU work is reduced when a block of inserts is performed.

Sorting your download and download delete cursor synchronization server scripts by primary key is recommended when synchronizing with BlackBerry smartphones. See Scripts to download rows.

Error reporting improvements for UltraLite BlackBerry smartphones when multiple applications connect to a database concurrently   A SQLE_FILE_IN_USE error is now reported if more than one application attempts to connect to an UltraLite Java edition database concurrently. See UltraLite and UltraLite Java edition database limitations.

AES 256-bit encryption and obfuscation for BlackBerry smartphones is now built in   You can enable encryption or obfuscation in your BlackBerry application by using the ConfigPersistent.enableAesDBEncryption or ConfigPersistent.enableObfuscation method in the UltraLiteJ API.

An -ek option has been added to several UltraLite Java edition utilities so that you can specify the encryption key needed to access encrypted databases.

See:

• Database security
• UltraLite Java edition utilities
• ConfigPersistent.enableAesDBEncryption method [UltraLiteJ]
• ConfigPersistent.enableObfuscation method [UltraLiteJ]
• ConfigPersistent.setEncryptionKey method [UltraLiteJ]
• ConfigPersistent.getEncryptionKey method [UltraLiteJ]
• Connection.changeEncryptionKey method [UltraLiteJ]

Custom user authentication messages can now be retrieved   Custom user authentication synchronization scripts on the MobiLink server now provide additional details with respect to the results of a synchronization's authentication.

A new system table, syssyncresult, has been added to the UltraLite management system to support this feature. This system table is a representation of the ul_sync_result structure.

For UltraLite Java edition, the SyncResult.getAuthMessage method can be used to retrieve the custom user authentication information.

See:

• syssyncresult system table
• ul_sync_result structure [UltraLite C and Embedded SQL datatypes]
• SyncResult.getAuthMessage method [UltraLiteJ]

UltraLite now caches rows   UltraLite now provides an additional layer of caching to take better advantage of the large memory capacity in modern devices. In addition to caching database pages in memory, a proportion of the assigned memory is allocated to caching individual rows for even faster access. The values supplied to cache control connection parameters now refer to the total memory allocated for caching, including the page cache and the row cache.

See:

• UltraLite CACHE_SIZE connection parameter
• UltraLite CACHE_MIN_SIZE connection parameter
• UltraLite CACHE_MAX_SIZE connection parameter
• UltraLite cache_allocation option