database.txt

Rockbuild uses an SQL database to store build history used for making
predictions about future build client performance.

This is how it is configured:

CREATE TABLE `builds` (
  `time` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00' ON UPDATE CURRENT_TIME
STAMP,
  `revision` varchar(48) NOT NULL,
  `id` varchar(64) NOT NULL,
  `client` varchar(64) NOT NULL,
  `timeused` decimal(6,2) NOT NULL,
  `bogomips` int(9) NOT NULL,
  `ultime` int(9) NOT NULL,
  `ulsize` int(9) NOT NULL,
  `errors` int(9) NOT NULL DEFAULT '1',
  `warnings` int(9) NOT NULL,
  `ramsize` int(9) NOT NULL,
  `binsize` int(9) NOT NULL,
  PRIMARY KEY (`revision`,`id`),
  KEY `revision` (`revision`),
  KEY `id` (`id`),
  KEY `client` (`client`),
  KEY `time` (`time`)
)

CREATE TABLE `clients` (
  `name` varchar(32) NOT NULL,
  `lastrev` varchar(48) NOT NULL,
  `totscore` int(9) NOT NULL,
  `builds` int(9) NOT NULL,
  `blocked` int(1) NOT NULL,
  PRIMARY KEY (`name`),
  KEY `lastrev` (`lastrev`),
  KEY `name` (`name`)
)

CREATE TABLE `log` (
  `revision` varchar(48) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAM
P,
  `client` varchar(32) NOT NULL,
  `type` varchar(16) NOT NULL,
  `value` varchar(128) NOT NULL,
  KEY `revision` (`revision`),
  KEY `client` (`client`)
)

CREATE TABLE `rounds` (
  `revision` varchar(48) NOT NULL,
  `took` int(9) NOT NULL,
  `clients` int(9) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAM
P,
  PRIMARY KEY (`revision`),
  KEY `revision` (`revision`)
)