Author: Michael Yee
Date: 17:45:49 03/14/05
Go up one level in this thread
On March 14, 2005 at 15:30:04, Dann Corbit wrote: >CREATE TABLE NumericParameters ( > NumericParameterID INTEGER NOT NULL, > ProgramID INTEGER NOT NULL, > ProgramVersionID INTEGER NOT NULL, > Name VARCHAR(255), > Description VARCHAR(255), > MinimumValue DOUBLE PRECISION, > MaximumValue DOUBLE PRECISION, > DefaultValue DOUBLE PRECISION, > CurrentValue DOUBLE PRECISION, > PreviousValue DOUBLE PRECISION >); Maybe this table could also have fields for StepSize and whether or not the parameter is restricted to be integer? >CREATE TABLE OpeningBook ( > OpeningBookID INTEGER NOT NULL, > FormatID INTEGER, > ProgramID INTEGER, > ProgramVersionID INTEGER, > BookName VARCHAR(255), > BookPath VARCHAR(20) >); Your database design looks really great (no surprise...). I especially like how it allows easy management of different configurations of the same engine. But is your scheme more of an implementation choice for how the GUI would manage its "installed" engines as opposed to part of the communication protocol? On a related note, I'm confused about where the FormatIDs for opening books would come from... Would they be harvested from the engines (i.e., we create a new ID every time an engine alerts the GUI about the existence of a new opening book format through a getoptions mechanism), or would they be pre-defined in some standard? Michael
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.