0005692: Option to disable the configuration database usage - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0005692	mantisbt	customization	public	2005-06-01 04:34	2005-07-23 02:31

Reporter	polzin	Assigned To	thraxisp
Priority	normal	Severity	feature	Reproducibility	N/A
Status	closed	Resolution	no change required
Product Version	1.0.0a2

Summary	0005692: Option to disable the configuration database usage
Description	For many cases the configuration in the database may have huge advantages. I would like to have the ability to switch it off. For someone how knows php programmed configuration setting depending on the project is more flexible and easier (you can use php to group projects) and better to maintain (you can put the php files under revision control). I ran into problems because the two config methods can interfere. Additionally, there may be a minor performance penalty for all the config_table queries. To do this, one could add easily a config_option in config_api.php:config_get. Perhaps not so easy is to find all places in the "Manage" menues that have to switched off. What do you think about this?
Tags	No tags attached.

thraxisp 2005-06-01 09:34 reporter ~0010317	You can do this in a parameter basis with the current code with some work. There is a config variable $g_globalsettings that lists variables that will never be looked up in the database. It is a comma separated list of variables without the $g prefix. If you add your settings to this, they will always come from config_inc.php

polzin 2005-06-01 09:52 reporter ~0010318	If I am the only one with this wish, this should be a suitable workaround. If you conjecture that others have the same desire, then there should be a global switching. Thanks.

thraxisp 2005-06-03 12:37 reporter ~0010351	It's even simpler, the pattern match used for the config variables is PCRE. Setting "$g_global_settings = '.*'; will match all settings and bypass the database settings.