comparison Sphinx/source/faq/orthanc-storage.rst @ 36:6474af38dcbd

SQLITE_BUSY
author Sebastien Jodogne <s.jodogne@gmail.com>
date Wed, 20 Jul 2016 15:19:08 +0200
parents 5737f51ff94e
children 38fb7bf24794
comparison
equal deleted inserted replaced
35:5737f51ff94e 36:6474af38dcbd
63 * Orthanc can be configured to compress the attachments before writing 63 * Orthanc can be configured to compress the attachments before writing
64 them on the disk (cf. the ``StorageCompression`` option). 64 them on the disk (cf. the ``StorageCompression`` option).
65 * By directly reading the content of ``OrthancStorage``, you bypass 65 * By directly reading the content of ``OrthancStorage``, you bypass
66 all the locking mechanisms used by Orthanc, which might result in 66 all the locking mechanisms used by Orthanc, which might result in
67 data corruption. 67 data corruption.
68 * One SQLite database should be accessed by at most one process at any
69 time to avoid any problem (e.g. with NFS filesystems), for reasons
70 that are `explained in the SQLite FAQ
71 <https://www.sqlite.org/faq.html#q5>`__. Orthanc will stop if it
72 receives the ``SQLITE_BUSY`` status.
68 73
69 As a consequence, it is **HIGHLY recommended NOT to directly access** 74 As a consequence, it is **HIGHLY recommended NOT to directly access**
70 the ``OrthancStorage`` folder and the SQLite database. Use the 75 the ``OrthancStorage`` folder and the SQLite database. Use the
71 :ref:`REST API <rest>` instead, which contains primitives to access 76 :ref:`REST API <rest>` instead, which contains primitives to access
72 the attachments (cf. the ``.../attachments/...`` URIs). 77 the attachments (cf. the ``.../attachments/...`` URIs).