An LXR database is defined either as a real independent database, or as an alternate table set in an existing database.
The new database is described by configuration parameters 'dbname'
,
'dbuser'
and 'dbpass'
.
'dbprefix'
can keep its default value.
The table names in the new set start with the prefix defined
by configuration parameter 'dbprefix'
.
The 'dbname'
, 'dbuser'
and 'dbpass'
parameters keep the same values for all trees.
Create the required data bases as you did for the first one.
Run script initdb-config.sh
for every new database (tree)
as explained in the
data base creation page.
Next process the resulting customised script through the database engine.
Run script initdb-config
to generate a customised
initdb-xxx
script
(xxx
= mysql
,
postgres
or oracle.sql
according to your choice of a relational database).
and answer questions. Next process the resulting customised script through the database engine.
lxr
),
you need to create it before running your customised script.
Follow these
instructions
replacing script initdb-xxx
with the custom one.
In the initdb-xxx
script
(xxx
= mysql
,
postgres
or oracle.sql
according to your choice of a relational database)
replace all occurrences of lxr_
by another prefix.
Run this script (without recreating the lxr
DB-user)
as explained in the page
"Create database".
initdb-xxx
scripts in a specific
way and eventually running extra commands.
You need to synchronise the Data storage subsection with what you did in the first step.
lxr
database,
you are free to keep the database parameters in the
tree-specific section or not.
Create a directory and copy its name either in
'glimpsedir'
or in 'swishdir'
:
Run the genxref
script
(
v0.11
or
prior versions)
for each tree.