From Eigenpedia

Jump to: navigation, search


LucidDB build is based on Farrago build

To build LucidDB from Perforce, follow the Farrago build instructions but with the modifications noted in the sections below.

Perforce client view

When mapping your Perforce client view, add a line for luciddb:

        //open/dev/thirdparty/... //YOURCLIENT/dev/thirdparty/...
        //open/dev/fennel/... //YOURCLIENT/dev/fennel/...
        //open/dev/farrago/... //YOURCLIENT/dev/farrago/...
        //open/dev/luciddb/... //YOURCLIENT/dev/luciddb/...


Instead of running from dev/farrago, run it from dev/luciddb instead. Also, there's no need to specify the --with-fennel parameter (this is the default for LucidDB builds).

Running programs

Instead of running programs and commands from dev/farrago, run them from dev/luciddb. The LucidDB build supports the following programs and commands:

  • sqllineEngine: as for Farrago, but sets the LucidDB personality
  • lucidDbServer: similar to farragoServer, but sets the LucidDB personality
  • sqllineClient: as for Farrago, but connects using the LucidDB JDBC driver
  • ant createCatalog: recreates the LucidDB catalog (which is stored separately from the Farrago catalog)
  • ant backupCatalog: backs up the LucidDB catalog
  • ant restoreCatalog: restores the LucidDB catalog
  • ant test: run LucidDB checkin acceptance tests
  • ant createEclipseProject: creates an Eclipse project for use in developing LucidDB code


LucidDB tracing is similar to Farrago's; settings are controlled by editing dev/luciddb/trace/, and output goes to LucidDbTrace.log in the same directory.