Use of LXR 0.11 is not recommended, unless you cannot upgrade your Perl interpretor to version 5.10 at least.

This release is frozen and still contains bugs which have been corrected in later releases. Only "compatibility" bugs will be accepted.

For performance reasons, LXR stores the references in a database. Presently, LXR cooperates with Postgresql, MySQL or Oracle, at your choice.

Creation

Database creation can only be done by a DB-user who has the privilege to create databases. Contact your site administrator if you can't or don't know how to proceed.

Configuration

DB table initialisation is done with interactive script initdb-config.sh. Default answer is shown uppercase. If it fits your need, just hit "return". Otherwise type your choice.

CAVEAT!
If you restart this step, first remove any initialisation script from lxrconf.d/ (command shown for default case): $ rm lxrconf.d/*.sql
$ ./scripts/initdb-config.sh *** initdb script configurator for LXR ($Revision: 1.3 $) *** In case you make a mistake, you can cancel the whole process by typing ctl-C. Which is your database engine? [MYSQL/oracle/postgres] > Which is your database name? [lxr] > Which table prefix will you use? [lxr_] > Under which user name will you connect to the database? [lxr] > Output script name? [lxrconf.d/initdb-mysql-custom.sql] > Your database engine is mysql Your database is lxr The tables are prefixed with lxr_ You connect as lxr Configuration script in lxrconf.d/initdb-mysql-custom.sql Is this correct? [YES|no] >
    Notes:
  1. In this example, the user accepted the default choices, which are adequate for the simple case of a single tree.
  2. The user name must be the same as the one given above.
  3. Remember your answers for database name, user and table prefix. They will be needed later.

If you answer yes, a DB table initialisation script is written in lxrconf.d/.

Init script saved in lxrconf.d/initdb-mysql-custom.sql

Multiple trees operation

Launch this script for every tree managed by LXR without changing the database engine; each partial output is appended to the end of the initialisation script.

Initialisation

The customised script is then processed by the database engine: