From a1430bfea56d8aa27656730d27ed780f1444bf97 Mon Sep 17 00:00:00 2001 From: drebs Date: Thu, 2 Nov 2017 12:41:07 -0200 Subject: [doc] improve client-side dbs doc --- docs/reference/client-database.rst | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/reference/client-database.rst b/docs/reference/client-database.rst index d8fd3be7..ac59c1bd 100644 --- a/docs/reference/client-database.rst +++ b/docs/reference/client-database.rst @@ -3,10 +3,21 @@ Client-side databases ===================== -Soledad Client uses `SQLCipher `_ for -storing data. The symmetric key used to unlock databases is chosen randomly and -stored encrypted with the user's passphrase (see :ref:`storage-secrets` for -more details). +These are some important information about Soledad's client-side databases: -:ref:`Documents ` and :ref:`blobs ` are stored in -different databases protected with the same symmetric secret. +- Soledad Client uses `SQLCipher `_ for + storing data. +- :ref:`Documents ` and :ref:`blobs ` are stored in + different databases protected with the same symmetric key. +- The symmetric key used to unlock databases is chosen randomly and is stored + encrypted by the user's passphrase (see :ref:`storage-secrets` for more details). + +The database files currently used in the client-side are: + +- ``.db``: The database for JSON documents storage. +- ``_blobs.db``: The database for storage of blobs. + +Depending on how local databases are configured, you may also find files with +the same names of the above but ending in ``-wal`` and ``-shm``, which +correspond to SQLCipher's `Write-Ahead Logging +`_ implementation. -- cgit v1.2.3