Basically, the idea was that
a) gmCfg/gmConfigData.sql supports only basic types (numeric,
string, str_array) while we might want some higher-level types (like
color, predefined ranges etc) later and
b) the admin might not want to hack sql-files to change/add config
options (at least I wouldn't)
...So actually the duplication of functionality is something I
wanted - although on a somewhat higher level than gmConfigData.sql.
I'm not sure if it really what we need or if something should be
changed/simplified.
The workflow I imagined was...