Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
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.
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. CREATE PUBLICATION statement [UltraLite] [UltraLiteJ] and ALTER PUBLICATION statement [UltraLite][UltraLiteJ].
Improved MobiLink client network layer Improvements to the client network layer include the following:
Synchronization compression is available for all protocols.
Persistent connections, so you can synchronize multiple times on the same connection.
Introduction of IPv6 support.
Improved error detection and debugging.
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 Additional Parameters synchronization parameter or any of the following:
Discuter à propos de cette page dans DocCommentXchange.
|Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0|