Bintracker Database Interface
The Bintracker Database holds information concerning an existing
installation of Bintracker. It is an SQLite3 database, managed through the
If Bintracker does not find
bt.db on application startup, it creates and
populates a fresh database.
mdefs table contains information about the installed MDAL
definitions. It contains the following columns:
id- definition name
version- engine version
hash- MD5 hash of the .mdef file
platform- target platform
description- configuration description
mdefs table is automatically updated during startup of Bintracker.
Open the Bintracker database, and point the symbol
btdb to it.
Close the Bintracker database.
(btdb-list-mdefs #!optional (PLATFORM 'any))
Returns the list of available MDAL definitions. The returned list has
(MDEF-ID, ENGINE-VERSION, TARGET-PLATFORM, DESCRIPTION).
Collect information on the MDAL definition named MDEF-ID into a
list, which has the form
(VERSION HASH TARGET-PLATFORM DESCRIPTION).
#f if the mdef is not found in the MDAL definition
Add the MDAL definition named MDEF-ID to the Bintracker database.
Remove the MDAL definition named MDEF-ID from the Bintracker database.
Update the MDAL definition named MDEF-ID in the Bintracker database.
Scan the MDAL mdef directory, and update the Bintracker database accordingly. Definitions no longer found in the mdef directory are deleted from the database, newly found definitions are added, and entries for modified definitions are updated.
Update the Bintracker Database on first run of the application.
mdefs table if necessary, then scans the MDAL mdef
directory for new or modified definitions and adds them to the database