Re: [Gnumed-devel] gnumed/client/etc/config-definitions/DBDefault.definitions vs. gnumed/sql/gmConfigData.sql

[Ian Haywood]

Hilmar Berger wrote:
> Hi,
> 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. 
Personally, I would be much happier with just one "offical" source for config 
metadata
(IOW, getting rid of the SQL table, or the config metadata file, I don't really 
care which)
This makes life much easier as a developer
> The workflow I imagined was 
> 1. you have some easy-to-use config-definitions, possibly containing default values that should be loaded at bootstrap/installation
Last time I checked, the config files didn't allow default values to be 
specified
(this is the big problem, there is no *one* place where you can specify 
everything), but that
should be easy to add.

We should also specify whether an option is machine-specific or not. This 
allows the
config editor to hide these details (as it is with this exposed it's too 
confusing for ordinary users)

In the fullness of time, we should forbid config options that don't have proper 
metadata.

Ian

signature.asc
Description: OpenPGP digital signature