Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 5041:5251e97b1de0
Configure the database backend in the config.ini
The database backend is currently configured in the 'db/backend_name'
file which is just another file that needs to be configured when setting
up or migrating a tracker instance. By moving this setting into the
config.ini it helps to reduce the number of files that need to be
configured and is more logical place for users to find the setting.
| author | John Kristensen <john@jerrykan.com> |
|---|---|
| date | Mon, 22 Dec 2014 13:30:20 +1100 |
| parents | cf22972fe080 |
| children | 5b2ce5723abb |
comparison
equal
deleted
inserted
replaced
| 5040:f52a9fb035d2 | 5041:5251e97b1de0 |
|---|---|
| 17 | 17 |
| 18 Contents: | 18 Contents: |
| 19 | 19 |
| 20 .. contents:: | 20 .. contents:: |
| 21 :local: | 21 :local: |
| 22 | |
| 23 Migrating from 1.5.1 to 1.6.0 | |
| 24 ============================= | |
| 25 | |
| 26 The ``db/backend_name`` file is no longer used to configure the database | |
| 27 backend being used for a tracker. The backend is now configured in the | |
| 28 ``config.ini`` file using the ``backend`` option located in the ``[rdbms]`` | |
| 29 section. For example if ``db/backend_name`` file contains ``sqlite``, a new | |
| 30 entry in the ``config.ini`` will need to be created:: | |
| 31 | |
| 32 [rdbms] | |
| 33 | |
| 34 ... | |
| 35 | |
| 36 # Database backend. | |
| 37 # Default: | |
| 38 backend = sqlite | |
| 39 | |
| 40 Once the ``config.ini`` file has been updated with the new ``backend`` option, | |
| 41 you can safely delete the ``db/backend_name`` file. | |
| 42 | |
| 43 Note: the ``backend_name`` file may be located in a directory other than | |
| 44 ``db/`` if you have configured the ``database`` option in the ``[main]`` | |
| 45 section of the ``config.ini`` file to be something other than ``db``. | |
| 22 | 46 |
| 23 Migrating from 1.5.0 to 1.5.1 | 47 Migrating from 1.5.0 to 1.5.1 |
| 24 ============================= | 48 ============================= |
| 25 | 49 |
| 26 User data visibility | 50 User data visibility |