# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1481706584 -3600
# Node ID 16d516fdc642afa413ac9498b7f12e8fa205f8fa
# Parent  a976607e46f7f8fa090ecc594703f14c80e1fa5f
note

diff -r a976607e46f7 -r 16d516fdc642 Sphinx/source/users/lua.rst
--- a/Sphinx/source/users/lua.rst	Wed Dec 14 09:43:53 2016 +0100
+++ b/Sphinx/source/users/lua.rst	Wed Dec 14 10:09:44 2016 +0100
@@ -16,7 +16,7 @@
 <https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Lua/>`__.
 
 
-Installing a Lua Script
+Installing a Lua script
 -----------------------
 
 .. highlight:: bash
@@ -198,7 +198,7 @@
 
 .. _lua-filter-dicom:
 
-Filtering Incoming DICOM Instances
+Filtering incoming DICOM instances
 ----------------------------------
 
 .. highlight:: lua
@@ -236,7 +236,7 @@
 
 .. _lua-filter-rest:
 
-Filtering Incoming REST Requests
+Filtering incoming REST requests
 --------------------------------
 
 .. highlight:: lua
@@ -284,7 +284,7 @@
 
 .. _lua-auto-routing:
 
-Auto-Routing of DICOM Images
+Auto-routing of DICOM images
 ----------------------------
 
 .. highlight:: lua
@@ -356,8 +356,8 @@
  end
 
 
-Important Remarks about Auto-Routing
-------------------------------------
+Important remarks about auto-routing
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 The ``SendToModality()``, ``SendToPeer()``, ``ModifyInstance()`` and
 ``Delete()`` functions are for the most basic cases of auto-routing
@@ -408,3 +408,11 @@
 (``OnStablePatient()``, ``OnStableStudy()`` and ``OnStableSeries()``)
 to react to other events than the reception of a single instance 
 with ``OnStoredInstance()``.
+
+
+Fixing C-Find
+-------------
+
+:ref:`C-Find requests <dicom-find>` are sometimes interpreted
+differently by different manufacturers (e.g. the ``*`` wildcard), and
+sometimes a querying modality sets 
diff -r a976607e46f7 -r 16d516fdc642 Sphinx/source/users/replication.rst
--- a/Sphinx/source/users/replication.rst	Wed Dec 14 09:43:53 2016 +0100
+++ b/Sphinx/source/users/replication.rst	Wed Dec 14 10:09:44 2016 +0100
@@ -9,9 +9,41 @@
 between :ref:`versions of the database schema <db-versioning>`, or to
 create **mirrored DICOM servers**.
 
-Note that if you only want to automatically upgrade the database for
-successive versions of Orthanc, you most probably only have to add the
-``--upgrade`` command-line option while starting Orthanc.
+
+Upgrade the database schema
+---------------------------
+
+As explained :ref:`elsewhere in the Orthanc Book <db-versioning>`,
+successive versions of Orthanc might use a different version of the
+database schema. If this happens, Orthanc will refuse to start (with
+an explicit message in its :ref:`logs <log>`), to let the user decides
+whether she actually wants to upgrade the database. At this point, the
+user might indeed decide to modify its :ref:`configuration file
+<configuration>` to create a new database elsewhere on the filesystem.
+
+If you decide to upgrade the database schema, you have to apply the
+following 3 steps:
+
+1. If not done yet, stop the running Orthanc service:
+
+   * Under Microsoft Windows, use the `services control panel
+     <https://en.wikipedia.org/wiki/Windows_service>`__.
+   * Under Debian, use ``sudo /etc/init.d/orthanc stop``.
+
+2. Manually call Orthanc with the ``--upgrade`` command-line option, 
+   and point to your default configuration file:
+
+   * Under Microsoft Windows, ``Orthanc.exe c:/Orthanc/``.
+   * Under Debian, use ``sudo /usr/sbin/Orthanc /etc/orthanc/ --upgrade``.
+
+3. Start the Orthanc service again:
+
+   * Under Microsoft Windows, use the `services control panel
+     <https://en.wikipedia.org/wiki/Windows_service>`__.
+   * Under Debian, use ``sudo /etc/init.d/orthanc stop``.
+
+Note that, depending on the size of the Orthanc database, upgrading
+the database schema might take time.
 
 
 Direct access to the filesystem