Mercurial > hg > orthanc-book

comparison Sphinx/source/faq/orthanc-storage.rst @ 272:07f109e3f3f7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
database schema
author Sebastien Jodogne <s.jodogne@gmail.com>
date Fri, 30 Aug 2019 09:22:34 +0200
parents 365427cebb64
children 6cbcdb965ad3
comparison
equal deleted inserted replaced
271:1173e40cbf35 272:07f109e3f3f7
49 Given one DICOM resource, all of its child attachments are identified 49 Given one DICOM resource, all of its child attachments are identified
50 by a number between 0 and 65535. Identifiers <= 1023 are reserved for 50 by a number between 0 and 65535. Identifiers <= 1023 are reserved for
51 the Orthanc core, whereas identifiers >= 1024 can be user-defined for 51 the Orthanc core, whereas identifiers >= 1024 can be user-defined for
52 external applications. 52 external applications.
53 53
54 Besides the attachments, the database index maintains other
55 information for each DICOM resource, notably the :ref:`metadata
56 <metadata>`, the :ref:`history of changes <changes>`, and an
57 associative map that stores the so-called "main" DICOM tags (to avoid
58 accessing the storage folder are when this is not needed). The SQLite
59 database schema is kept as simple as possible, and can be found in the
60 following two files of the source code of Orthanc:
61 `PrepareDatabase.sql
62 <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.5.7/OrthancServer/Database/PrepareDatabase.sql>`__
63 and `InstallTrackAttachmentsSize.sql
64 <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.5.7/OrthancServer/Database/InstallTrackAttachmentsSize.sql>`__.
65
54 66
55 Direct access 67 Direct access
56 ------------- 68 -------------
57 69
58 Directly accessing the content of the ``OrthancStorage`` folder and 70 Directly accessing the content of the ``OrthancStorage`` folder and