Mercurial > hg > orthanc-book

comparison Sphinx/source/faq/orthanc-storage.rst @ 154:365427cebb64

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mysql
author Sebastien Jodogne <s.jodogne@gmail.com>
date Tue, 10 Jul 2018 14:45:40 +0200
parents 12b204ee328d
children 07f109e3f3f7
comparison
equal deleted inserted replaced
153:008091376e7a 154:365427cebb64
5 5
6 Storage folder 6 Storage folder
7 -------------- 7 --------------
8 8
9 **By default** (i.e. if no database plugin such as :ref:`PostgreSQL 9 **By default** (i.e. if no database plugin such as :ref:`PostgreSQL
10 <postgresql>` is used), Orthanc stores all the DICOM files it receives 10 <postgresql>` or :ref:`MySQL <mysql>` is used), Orthanc stores all the
11 in a folder called ``OrthancStorage`` on the filesystem. Orthanc also 11 DICOM files it receives in a folder called ``OrthancStorage`` on the
12 associates each incoming DICOM file with a JSON file that summarizes 12 filesystem. Orthanc also associates each incoming DICOM file with a
13 all its DICOM tags, which speeds up subsequent processing by avoiding 13 JSON file that summarizes all its DICOM tags, which speeds up
14 a costly DICOM parsing. 14 subsequent processing by avoiding a costly DICOM parsing.
15 15
16 More generally, the ``OrthancStorage`` folder contains a set of 16 More generally, the ``OrthancStorage`` folder contains a set of
17 so-called **attachments**, that may correspond to either a DICOM file, 17 so-called **attachments**, that may correspond to either a DICOM file,
18 a JSON file, or any user-defined file. Internally, each attachment is 18 a JSON file, or any user-defined file. Internally, each attachment is
19 automatically associated with an `universally unique identifier (UUID) 19 automatically associated with an `universally unique identifier (UUID)
58 Directly accessing the content of the ``OrthancStorage`` folder and 58 Directly accessing the content of the ``OrthancStorage`` folder and
59 the content of the SQLite database is strongly discouraged for several 59 the content of the SQLite database is strongly discouraged for several
60 reasons: 60 reasons:
61 61
62 * This internal organization is only true when no database plugin is 62 * This internal organization is only true when no database plugin is
63 used (e.g. the :ref:`PostgreSQL plugin <postgresql>` can be 63 used (e.g. the :ref:`PostgreSQL <postgresql>` and :ref:`MySQL
64 configured to store the attachments inside a database). 64 <mysql>` plugins can be configured to store the attachments inside a
65 database).
65 * Orthanc can be configured to compress the attachments before writing 66 * Orthanc can be configured to compress the attachments before writing
66 them on the disk (cf. the ``StorageCompression`` option). 67 them on the disk (cf. the ``StorageCompression`` option).
67 * By directly reading the content of ``OrthancStorage``, you bypass 68 * By directly reading the content of ``OrthancStorage``, you bypass
68 all the locking mechanisms used by Orthanc, which might result in 69 all the locking mechanisms used by Orthanc, which might result in
69 data corruption. 70 data corruption.