UltraLite Database User's Guide
   Synchronization for UltraLite Applications
    Designing synchronization for your UltraLite database

Designing sets of data to synchronize separately

The schema of an UltraLite database is defined by the queries included in the application. You can add publications to the reference database to define sets of data that can be synchronized separately. If you do not use publications to define which changes are to be synchronized, all changes are synchronized.

Publications are used for several purposes in SQL Anywhere. A publication consists of a set of articles. In general, each article can be a whole table, or can define a subset of the data in a table.

Articles defined for UltraLite applications can use row subsets by supplying a WHERE clause, but cannot use column subsets or the SUBSCRIBE BY clause. Articles in UltraLite publications governing HotSync synchronization cannot use a WHERE clause.

To synchronize subsets of data from an UltraLite database

1. Create publications representing the data you wish to synchronize.

   For more information, see Creating publications for UltraLite databases.

2. Run the UltraLite generator, specifying the publications on the -v command-line option.

   For more information, see The UltraLite generator.

3. When calling the synchronization function, specify the publication.

   If you specify no publication, all changes to the database are synchronized. If you specify one or more publications, only changes that fall within one or more of the listed publications are synchronized.

   For more information, see the following:

   • MobileVB    See SyncParms.

   • ActiveX    See SyncParms.

   • Native UltraLite for Java    See ianywhere.native_ultralite.SyncParms in the API Reference.

   • Embedded SQL    See publication synchronization parameter.

   • Static C++ API    See publication synchronization parameter.

   • Static Java API    See publication synchronization parameter.

Creating publications for UltraLite databases