Contents Index Including read-only tables in an UltraLite database Foreign key cycles

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

Using client-specific data to control synchronization


Some UltraLite applications require client-specific data that control synchronization, but which are not needed on the consolidated database. For example, you may wish your UltraLite applications to indicate which of a number of channels or topics they are interested in, and use this information to download the appropriate rows.

If you create a table in your UltraLite database with a name ending in allsync, all rows of that table are synchronized at each synchronization, whether or not they have been changed since the last synchronization.

You can store user-specific or client-specific data in allsync tables. If you upload the data in the table to a temporary table in the consolidated database on synchronization, you can use the data to control synchronization by your other scripts without having to be maintained in the consolidated database.


Contents Index Including read-only tables in an UltraLite database Foreign key cycles