Differences

This shows you the differences between two versions of the page.

--- dev:accessing_zotero_data_using_an_sqlite_client [2009/11/06 14:48] – dstillman
+++ dev:accessing_zotero_data_using_an_sqlite_client [2011/04/16 15:40] – rmzelle
@@ Line 1: / Line 1: @@
-Whenever possible, people writing utilities that access Zotero data should use the [[ interacting_with_zotero_from_within_firefox#the_zotero_data_api|Zotero data API]] from within Firefox, as it provides both a consistent interface to the data regardless of the underlying structure (which may change with updates to the software) as well as a notification system for data modifications. However, since SQLite is an open format, users and developers have the option of using the SQLite client/library or third-party tools to access Zotero data.
+See [[dev/client_coding/Direct SQLite Database Access]].
-It is important to note, however, that **external access to the SQLite database (including direct access via the mozStorage API) should only be done in a read-only manner.** Modifying the database while Zotero is running can easily result in a corrupted database, as mozStorage caching breaks the normal file-locking in SQLite that allows concurrent file access to be done safely. And even if Firefox is shut down before accessing the file, modifying the database directly bypasses the data validation and referential integrity checks performed by Zotero that are required for Zotero to function properly (and which aren’t provided by SQLite itself). Generally, the SQLite database should be viewed as an internal database that has the benefit of being externally readable for people who want to get the data out in other ways.