Mathieu Lirzin <m...@gnu.org> skribis: > Hello, > > l...@gnu.org (Ludovic Courtès) writes: > >> Mathieu Lirzin <m...@gnu.org> skribis: >> > [...] >>> CREATE TABLE Specifications ( >>> id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, >>> repo_name TEXT NOT NULL, >>> url TEXT NOT NULL, >>> load_path TEXT NOT NULL, >>> file TEXT NOT NULL, >>> proc TEXT NOT NULL, >>> arguments TEXT NOT NULL, >>> -- The following columns are optional. >>> branch TEXT, >>> tag TEXT, >>> revision TEXT >>> ); >>> >>> CREATE TABLE Evaluations ( >>> derivation TEXT NOT NULL PRIMARY KEY, >>> job_name TEXT NOT NULL, >>> specification INTEGER NOT NULL, >>> FOREIGN KEY (specification) REFERENCES Specifications (id) >>> ); >> >> An evaluation leads to several derivations (for Guix, roughly one >> derivation per package and per system type), but the table above seems >> to suggest that each evaluation is mapped to only one derivation? > > In my "confused" mind each derivation was considered an individual > evaluation. But as you pointed out this makes more sense to decouple > those. Fixed in commit d493a58823aed8c556bf795d02207e57718b96c9
Perfect, thanks! Ludo’.
