![]() "dbfile", especially when the context is the Zumero server. When we speak of a SQLite database file, we often use the term Any dbfile name that begins with "zumero_" is reserved for internal use. The name may contain only lower-case letters,ĭigits, or underscores. The Zumero server is very particular about how each SQLite database Unlike the filesystem abstraction presented on aĬlient, the server's abstraction is a flat list, not a For the purpose of identifying which one is which, each The Zumero server can manage a collection of SQLite database When you open the file (using, say, sqlite3_open_v2() from the You want, and the path of that file is the identifier you use to access ![]() Using the SQLite API (or some wrapper around it). On the client, all of your interaction with the SQLite database file takes place Managing two copies of a SQLite database file, one on the client, and the other When you perform a zumero_sync() operation, you are Security features such as authentication and access control lists. Synchronization services (with conflict resolution) for mobile devices.Ī centralized, authoritative copy of your data. zumero_quarantine_since_last_sync() 10.6.2. zumero_get_storage_usage_on_server() 10.2. zumero_internal_auth_set_acl_entry() 10.1.8. zumero_internal_auth_set_password() 10.1.7. UNIQUE constraints: An ounce of prevention 5.2.5. Adding columns to an existing table 3.7.3. ![]() Limitations of SQLite virtual tables 3.7.1. Optional feature: Strict Type Checking 3.7.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |