From 3fb56b4760b0485cf0872100f04b0a5a51f52e97 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Karel=20Ko=C4=8D=C3=AD?= Date: Mon, 17 Aug 2015 18:35:12 +0200 Subject: Generated configuration is now fully stored to database Managing configurations in files and in database could cause inconsistence. Adding all generated configurations to database allow us to clean project files without loosing data. --- scripts/databaseinit.sql | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'scripts/databaseinit.sql') diff --git a/scripts/databaseinit.sql b/scripts/databaseinit.sql index 1e34c75..d1ab3e2 100644 --- a/scripts/databaseinit.sql +++ b/scripts/databaseinit.sql @@ -17,7 +17,7 @@ CREATE TABLE configurations ( id BIGSERIAL PRIMARY KEY, -- Id hash char(32) NOT NULL, -- Hash of configuration generator TEXT NOT NULL, -- Text identificator of configure generation method - cfile TEXT NOT NULL, -- File path with configuration + config TEXT NOT NULL, -- Full configuration in text form gtime timestamp NOT NULL, -- Time and date of generation linuxgit BIGINT REFERENCES linuxgit (id), -- Reference to git version of Linux toolgit BIGINT REFERENCES toolsgit (id) -- Reference to git version of tools @@ -34,3 +34,10 @@ CREATE TABLE measure ( linuxgit BIGINT REFERENCES linuxgit (id), -- Reference to git version of Linux toolgit BIGINT REFERENCES toolsgit (id) -- Reference to git version of tools ); + +-- In this table are sorted all used configuration options +-- Order in this table is fundamental for configuration hash calculation +CREATE TABLE configopt ( + id BIGSERIAL PRIMARY KEY, -- Id + configopt TEXT NOT NULL -- Name of configuration option +); -- cgit v1.2.3