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

[Hilmar Berger]

> development I don't see the necessity to provide intermediate
> level tools. Either the admin knows what she is doing (and
> then she can just edit the database) or she is a user and
> better get hold of an admin. Once we got nothing else to do we
> can ease the admin's life to no end.
As I mentioned before, I don't believe that learning the table structure of 
config data is something an admin will want to do. Additionaly, the tools to 
set/read config options from/to a text file is already there and working 
(client/pycommon/tools/transferDBset.py, mentioned the wrong file in my last 
post). So I don't see why anybody should have to edit gmConfigData.sql. That 
doesn't mean that you can't do it, though.

Hilmar 

> Karsten
> -- 
> GPG key ID E4071346 @ wwwkeys.pgp.net
> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
> 
> 
> _______________________________________________
> Gnumed-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnumed-devel
> 


--