Configurable and increased default cache size for HotSync conduit synchronization    Previously, beyond a certain amount of data synchronized on Palm OS file-based data stores, synchronization speeds were negatively affected. Consequently, the default cache size (on desktop) for the UltraLite conduit has been increased to 4 MB. This increased cache size significantly improves the synchronization time by cutting down unnecessary file I/O operations. However, you can also configure a different default cache size if you choose. See UltraLite HotSync Conduit Installation utility for Palm OS (ulcond11).

Predicates on publications   Synchronization publications for UltraLite now allow predicates. If you want to optionally combine conditional expressions with the logical operators AND and OR, you can now define this set of conditions in a WHERE or HAVING clause. As with SQL Anywhere, a predicate that evaluates to UNKNOWN is interpreted as FALSE. UltraLite CREATE PUBLICATION statement and UltraLite ALTER PUBLICATION statement.

Improved MobiLink client network layer   Improvements to the client network layer include the following:

For more information on using UltraLite as a client to MobiLink, see UltraLite clients.

Set table order for synchronization   Synchronization from UltraLite clients now includes the ability to specify table ordering to avoid referential integrity issues during table upload. If you want to specify table order for synchronization, use the table_order synchronization parameter. See either Table Order synchronization parameter or any of the following:

• UltraLite.NET: ULSyncParms class
• UltraLite C/C++: ul_synch_info_a struct
• UltraLite for M-Business Anywhere: SyncParms class
• UltraLite for embedded SQL: ULGetSynchResult function